Triple
T4467369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gazi |
E98410
|
entity |
| Predicate | titlePosition |
P21675
|
FINISHED |
| Object | prefixed to personal name |
—
|
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: prefixed to personal name | Statement: [Gazi, titlePosition, prefixed to personal name]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titlePosition Context triple: [Gazi, titlePosition, prefixed to personal name]
-
A.
titlePositionRelation
chosen
Indicates a relationship specifying how a title is positioned or ordered relative to other titles or elements.
-
B.
titleHolderTo
Indicates that one entity currently holds or possesses an official title, position, or designation in relation to another entity.
-
C.
titleVariant
Indicates that one title is an alternative or variant form of another title referring to the same work or entity.
-
D.
titleOrRole
Indicates that one entity serves as the title, position, or role held or described by another entity.
-
E.
titleStart
Indicates that one entity’s title begins with the text or substring represented by the other entity.
- 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_69b3454b4ae481908967426dd37284d6 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b356fb69a0819099f0005779f4fcac |
completed | March 13, 2026, 12:14 a.m. |
| PD | Predicate disambiguation | batch_69b3563bf4f8819081726cde3a34460b |
completed | March 13, 2026, 12:11 a.m. |
Created at: March 12, 2026, 11:34 p.m.