Triple
T3736804
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Persian literature |
E79604
|
entity |
| Predicate | hasGoldenAge |
P51363
|
FINISHED |
| Object | 10th century |
—
|
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: 10th century | Statement: [Persian literature, hasGoldenAge, 10th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGoldenAge Context triple: [Persian literature, hasGoldenAge, 10th century]
-
A.
hasAge
Indicates that an entity possesses a specific age value, typically expressed as a number of time units since its birth or creation.
-
B.
hasLegacy
Indicates that an entity leaves behind a lasting impact, influence, or inheritance that continues to exist or be recognized over time.
-
C.
hasAgeTransformation
Indicates a relationship where an entity undergoes or causes a change in age or age-related state.
-
D.
endedInDecade
Indicates that an event, process, or state concluded during a specified decade.
-
E.
hasAncientMember
Indicates that at least one member of a group, set, or collection originates from or belongs to an ancient time period.
- F. None of above. chosen
Provenance (4 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_69ad8b115610819095b02007da5ca3cb |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcb3d32b081909a993a78b0869db8 |
completed | March 8, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69adc04746588190b0dc535638f23546 |
completed | March 8, 2026, 6:30 p.m. |
| PDg | Predicate description generation | batch_69adc45debe48190b1c1f894e02b0316 |
completed | March 8, 2026, 6:47 p.m. |
Created at: March 8, 2026, 3:34 p.m.