Triple
T4518198
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Janissary Agha |
E103203
|
entity |
| Predicate | wasTitleFor |
P14143
|
FINISHED |
| Object | head of the Janissary corps |
—
|
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: head of the Janissary corps | Statement: [Janissary Agha, wasTitleFor, head of the Janissary corps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasTitleFor Context triple: [Janissary Agha, wasTitleFor, head of the Janissary corps]
-
A.
namedForTitle
Indicates that one entity is named after or in honor of the title (such as a rank, honorific, or formal designation) associated with another entity.
-
B.
hadTitle
Indicates that an entity held or was assigned a specific title or formal designation.
-
C.
usesTitle
Indicates that one entity refers to or addresses another entity using a specific title or formal designation.
-
D.
isTitleFor
chosen
Indicates that one entity serves as the official title or name designation for another entity.
-
E.
eraTitleWith
Indicates a relationship where a specific era is associated with or designated by a particular title.
- 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_69bd43dba59881908cf59b31df8c7ae1 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd57465a10819086866e29f7a6eb02 |
completed | March 20, 2026, 2:18 p.m. |
| PD | Predicate disambiguation | batch_69bd521abea48190b3e758a1f98dd55e |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:02 p.m.