Triple
T2017968
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coat of arms of Yemen |
E44038
|
entity |
| Predicate | MaribDamSymbolism |
P34524
|
FINISHED |
| Object | ancient Sabaean civilization |
—
|
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: ancient Sabaean civilization | Statement: [Coat of arms of Yemen, MaribDamSymbolism, ancient Sabaean civilization]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: MaribDamSymbolism Context triple: [Coat of arms of Yemen, MaribDamSymbolism, ancient Sabaean civilization]
-
A.
reservoirCreatedByDam
Indicates that a reservoir exists as a result of being formed or impounded by a specific dam.
-
B.
watercourseHasDam
Indicates that a watercourse (such as a river or stream) has a dam constructed on or across it.
-
C.
hasMaritimeMuseum
Indicates that one entity possesses, hosts, or includes a maritime museum as part of its features or facilities.
-
D.
hasMaritimeHeritage
Indicates that an entity possesses a historical, cultural, or traditional connection to maritime activities, seafaring, or the sea.
-
E.
majorPortOnRiver
Indicates that a port is a primary or significant harbor facility located on the banks of a specified river.
- 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_69a8891201bc8190aca837be6de41579 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb8ce71788190ac21beff10b08122 |
completed | March 7, 2026, 5:34 a.m. |
| PD | Predicate disambiguation | batch_69abb7a389408190a84a54856352f15b |
completed | March 7, 2026, 5:29 a.m. |
| PDg | Predicate description generation | batch_69abb83e7888819096dc40275c77daff |
completed | March 7, 2026, 5:31 a.m. |
Created at: March 4, 2026, 7:38 p.m.