Triple
T14603188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Half of the World |
E342752
|
entity |
| Predicate | appliedByTradition |
P13958
|
FINISHED |
| Object | Persian chroniclers |
—
|
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: Persian chroniclers | Statement: [Half of the World, appliedByTradition, Persian chroniclers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliedByTradition Context triple: [Half of the World, appliedByTradition, Persian chroniclers]
-
A.
traditionAscribes
chosen
Indicates that a tradition attributes or assigns a particular quality, role, origin, or action to an entity.
-
B.
establishedTradition
Indicates that something has become a customary, long-standing practice or convention that is regularly followed within a group, culture, or context.
-
C.
hasUseInTradition
Indicates that something is employed or holds a functional role within a particular cultural, religious, or historical tradition.
-
D.
mainTradition
Indicates that one entity represents the primary or dominant tradition associated with another entity.
-
E.
practicedTradition
Indicates that an entity engages in or carries out a particular tradition as a customary or repeated practice.
- 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_69d822dec68081908c2553145c4051dc |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb43a1bb48190bf520cb961f15b5e |
completed | April 14, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69de656f9f4c81909f815b6629a9ee39 |
completed | April 14, 2026, 4:03 p.m. |
Created at: April 10, 2026, 1:25 a.m.