Triple
T4434033
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Luxor Temple |
E95602
|
entity |
| Predicate | majorTouristDestinationSince |
P55985
|
FINISHED |
| Object | 19th century |
—
|
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: 19th century | Statement: [Luxor Temple, majorTouristDestinationSince, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorTouristDestinationSince Context triple: [Luxor Temple, majorTouristDestinationSince, 19th century]
-
A.
isTouristDestination
Indicates that a place is recognized as a location people commonly visit for leisure, sightseeing, or travel.
-
B.
hasTouristRank
Indicates that an entity is assigned a specific rank or rating based on its attractiveness or importance as a tourist destination.
-
C.
hasMajorHistoricalCentersIn
Indicates that an entity possesses significant, historically important centers or hubs located within a specified place or region.
-
D.
majorCityObserved
Indicates that an observation or event has been recorded as occurring in, or being associated with, a major city.
-
E.
isMajorAttractionFor
Indicates that something serves as a primary or highly significant draw or point of interest for a particular audience, group, or location.
- 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_69b3453ea2b48190a26f154b3b8fece5 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b35587bc048190aee8e0ed94b6e064 |
completed | March 13, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69b34f6078cc8190831b89f404198cc5 |
completed | March 12, 2026, 11:42 p.m. |
| PDg | Predicate description generation | batch_69b3505a87b4819083fbbd58870e520b |
completed | March 12, 2026, 11:46 p.m. |
Created at: March 12, 2026, 11:31 p.m.