Triple
T36711256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yehud (Hellenistic province) |
E906798
|
entity |
| Predicate | approximateStartAfter |
P182965
|
FINISHED |
| Object | conquests of Alexander the Great |
—
|
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: conquests of Alexander the Great | Statement: [Yehud (Hellenistic province), approximateStartAfter, conquests of Alexander the Great]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateStartAfter Context triple: [Yehud (Hellenistic province), approximateStartAfter, conquests of Alexander the Great]
-
A.
timeStartApprox
Indicates that the associated event or state begins at an approximate, rather than exact, point in time.
-
B.
arisesAfter
chosen
Indicates that one event, state, or condition comes into existence or begins only after another specified event, state, or condition has occurred.
-
C.
approximateAscentTime
Indicates the estimated amount of time required for an entity to ascend or climb to a specified point or elevation.
-
D.
startsAt
Indicates that an event, process, or state begins at a specific time, location, or point in a sequence.
-
E.
activePeriodApproximate
Indicates that the time span during which an entity was active is known only approximately rather than as precise dates.
- 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_69f76e73ad108190a5241585f2303e9a |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ff8aff48988190a48a440de8238ef9 |
completed | May 9, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69ff8a780404819082f48ceb21e7fe11 |
completed | May 9, 2026, 7:26 p.m. |
Created at: May 3, 2026, 4:12 p.m.