Triple
T33467236
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Theban region |
E857086
|
entity |
| Predicate | modernUrbanCenter |
P48921
|
FINISHED |
| Object | Luxor |
—
|
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: Luxor | Statement: [Theban region, modernUrbanCenter, Luxor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modernUrbanCenter Context triple: [Theban region, modernUrbanCenter, Luxor]
-
A.
modernCityIs
Indicates that something possesses the characteristics or status of being a modern city.
-
B.
mainUrbanTerminus
Indicates the primary urban endpoint or central city location where a route, line, or service terminates.
-
C.
developedUrbanCenters
Indicates that an entity has created, expanded, or significantly contributed to the growth of urban population centers or cities.
-
D.
majorUrbanCenterIn
chosen
Indicates that a city or metropolitan area functions as a primary or significant urban center within the specified region or administrative unit.
-
E.
urbanCoreCity
Indicates that a city functions as the primary urban core or central city within a larger metropolitan or urban area.
- 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_69f34973461481909c701c98ebd75623 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd19f791f48190bbb6f6047f9ddc59 |
completed | May 7, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69fd0df365948190bc9bfc7ffd46acd8 |
completed | May 7, 2026, 10:10 p.m. |
Created at: May 1, 2026, 1:37 a.m.