Triple
T4518188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aga of the Janissaries |
E103202
|
entity |
| Predicate | hadSymbol |
P52874
|
FINISHED |
| Object | distinctive Janissary insignia |
—
|
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: distinctive Janissary insignia | Statement: [Aga of the Janissaries, hadSymbol, distinctive Janissary insignia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadSymbol Context triple: [Aga of the Janissaries, hadSymbol, distinctive Janissary insignia]
-
A.
hasSacredSymbol
Indicates that one entity serves as a sacred or religiously significant symbol associated with another entity.
-
B.
hasScar
Indicates that one entity bears or possesses a scar on its body.
-
C.
hasTraditionalSymbol
Indicates that something is associated with or represented by a conventional or culturally established symbol.
-
D.
hasSign
Indicates that an entity possesses, displays, or is associated with a particular sign or symbol.
-
E.
haveOfficialSymbols
chosen
Indicates that an entity possesses formally recognized symbols (such as flags, emblems, or insignia) that officially represent it.
- 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.