Triple
T23996090
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Azd |
E605192
|
entity |
| Predicate | originAreaTraditional |
P83441
|
FINISHED |
| Object | Yemen |
—
|
NE NERFINISHED |
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: Yemen | Statement: [Azd, originAreaTraditional, Yemen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originAreaTraditional Context triple: [Azd, originAreaTraditional, Yemen]
-
A.
onTraditionalCountryOf
Indicates that something is located within or associated with the traditional country or ancestral lands of a particular group.
-
B.
hasTraditionalArea
Indicates that an entity is associated with or belongs to a customary or historically recognized geographic area.
-
C.
locatedInTraditionalRegion
Indicates that an entity is situated within a specific traditional or historically recognized region.
-
D.
hasTraditionalTerritoryType
Indicates that an entity’s traditional territory is classified as belonging to a specific type or category of territory.
-
E.
originalTerritory
chosen
Indicates that a specified area or region is the initial or historically established domain associated with an entity before any changes, transfers, or expansions.
- 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.