Triple
T23996092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Azd |
E605192
|
entity |
| Predicate | migrationReasonTraditional |
P42539
|
FINISHED |
| Object | collapse of the Marib Dam |
—
|
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: collapse of the Marib Dam | Statement: [Azd, migrationReasonTraditional, collapse of the Marib Dam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: migrationReasonTraditional Context triple: [Azd, migrationReasonTraditional, collapse of the Marib Dam]
-
A.
historicalMigrationType
Indicates the type or category of migration that occurred in a historical context between entities.
-
B.
mainTradition
Indicates that one entity represents the primary or dominant tradition associated with another entity.
-
C.
migrationCause
chosen
Indicates the reason or driving factor that leads an entity to migrate from one place to another.
-
D.
traditionMergedInto
Indicates that one tradition has been absorbed into, combined with, or continued within another tradition, ceasing to exist as a separate entity.
-
E.
traditionSince
Indicates that a tradition has been continuously practiced or recognized starting from a specified point in time.
- 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_69e295463f7c8190b1c19dbd114641b9 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d38f8a208190a293c64b9c9202c0 |
completed | April 29, 2026, 9:46 a.m. |
| PD | Predicate disambiguation | batch_69f1615994c48190a5de95d3f7e5cd0a |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 9:38 p.m.