Triple
T9334581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marib Dam |
E224611
|
entity |
| Predicate | finalMajorFailureApproxDate |
P37360
|
FINISHED |
| Object | around 570 CE |
—
|
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: around 570 CE | Statement: [Marib Dam, finalMajorFailureApproxDate, around 570 CE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalMajorFailureApproxDate Context triple: [Marib Dam, finalMajorFailureApproxDate, around 570 CE]
-
A.
finalDefeatDate
Indicates the date on which an entity was ultimately and conclusively defeated.
-
B.
finalAppTransitionDate
Indicates the date on which the final transition or change of state for the application was completed.
-
C.
collapseDate
chosen
Indicates the date on which something structurally or functionally failed, broke down, or ceased to exist.
-
D.
finalDeliveryDate
Indicates the date on which the last or ultimate delivery in a sequence of deliveries is scheduled or actually occurs.
-
E.
decayDate
Indicates the date on which something ceases to be valid, effective, or usable (i.e., when it expires or decays).
- 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_69ca84286fcc81909f6e7fd7a7e862a2 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd37ee53988190bcc76588edbc2858 |
completed | April 1, 2026, 3:21 p.m. |
| PD | Predicate disambiguation | batch_69cc7a643924819097f01144734901cf |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:39 p.m.