Triple
T35661783
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JapaneseHonorificTitles |
E1030452
|
entity |
| Predicate | includesPrefix |
P93740
|
FINISHED |
| Object | o- |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: o- | Statement: [JapaneseHonorificTitles, includesPrefix, o-]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesPrefix Context triple: [JapaneseHonorificTitles, includesPrefix, o-]
-
A.
hasPrefix
Indicates that one entity occurs at the beginning of another entity, serving as its starting segment or initial substring.
-
B.
usedAsPrefixIn
chosen
Indicates that one element functions as a leading prefix component in the formation or representation of another element.
-
C.
includesMatch
Indicates that one entity contains or encompasses a particular match or matching instance of another entity.
-
D.
includesFinal
Indicates that one entity contains or encompasses another entity as its concluding or last part.
-
E.
usesTrunkPrefix
Indicates that one entity employs a specific trunk dialing prefix when initiating calls or connections through a telecommunication system.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f76e09f87881909c954aaac176c34f |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a04d8348190a4819666eab42c9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:05 p.m.