Triple
T22615018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thinite nome |
E558120
|
entity |
| Predicate | positionInRegion |
P75615
|
FINISHED |
| Object | southern Egypt |
—
|
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: southern Egypt | Statement: [Thinite nome, positionInRegion, southern Egypt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInRegion Context triple: [Thinite nome, positionInRegion, southern Egypt]
-
A.
positionOnTerritory
chosen
Indicates that one entity occupies or is located at a specific position within the spatial extent of another entity’s territory.
-
B.
hasRegionalPosition
Indicates that one entity holds a specific role, status, or placement within a defined geographic or regional context relative to another entity.
-
C.
positionInSector
Indicates the specific location or placement of an entity within a defined sector or sub-area.
-
D.
positionInState
Indicates that one entity occupies or holds a specific position, role, or status within a particular state or condition of another entity.
-
E.
positionInCase
Indicates the specific role, status, or placement that an entity holds within a particular case or legal proceeding.
- 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_69e24545a8e08190bfa7482a2c725ff1 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f167ecc7188190bf41fe2177d48e6c |
completed | April 29, 2026, 2:07 a.m. |
| PD | Predicate disambiguation | batch_69ee62855558819080da946c7b35a160 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 17, 2026, 2:59 p.m.