Triple
T38434184
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anazah |
E903889
|
entity |
| Predicate | historicallyMobileAcross |
P203915
|
FINISHED |
| Object | Arabian Peninsula |
E7627
|
NE 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: Arabian Peninsula | Statement: [Anazah, historicallyMobileAcross, Arabian Peninsula]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicallyMobileAcross Context triple: [Anazah, historicallyMobileAcross, Arabian Peninsula]
-
A.
historicalPlatform
Indicates that an entity served as a platform or venue for another entity during a past or historically specific period.
-
B.
historicallyUsedFor
Indicates that something served a particular function or purpose at some point in the past, even if it may no longer be used that way now.
-
C.
widthHistorical
Indicates that an entity’s width is recorded or characterized as it existed at some point in the past, rather than its current width.
-
D.
historicallyIn
Indicates that one entity existed, occurred, or was situated within the historical context, period, or jurisdiction associated with another entity.
-
E.
historicallyReplaced
Indicates that one entity took the place of another in fulfilling a similar role or function at some point in history.
- F. None of above. chosen
Provenance (5 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_69f76e6a2024819081aa04f4932f89d2 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a02efcb13248190a0bef09ba7869ada |
completed | May 12, 2026, 9:15 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41cca7567c8190988d9361ea86188b |
completed | June 29, 2026, 1:38 a.m. |
| PD | Predicate disambiguation | batch_6a024995e1d081908783ca294d1397c3 |
completed | May 11, 2026, 9:26 p.m. |
| PDg | Predicate description generation | batch_6a02efca70c48190b724c2a76a09cbfb |
completed | May 12, 2026, 9:15 a.m. |
Created at: May 3, 2026, 4:31 p.m.