Triple
T9856129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miner’s Landing |
E239589
|
entity |
| Predicate | cityTourStopFor |
P56381
|
FINISHED |
| Object | Seattle city tours |
—
|
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: Seattle city tours | Statement: [Miner’s Landing, cityTourStopFor, Seattle city tours]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cityTourStopFor Context triple: [Miner’s Landing, cityTourStopFor, Seattle city tours]
-
A.
tourStopOf
chosen
Indicates that one entity is a stop or scheduled visit location within the itinerary or route of another entity’s tour.
-
B.
touristAttractionIn
Indicates that a place functions as a tourist attraction located within a specified geographic area or entity.
-
C.
hasTouristAttractionRole
Indicates that an entity serves in the capacity or function of a tourist attraction for another entity (such as a place, organization, or area).
-
D.
cityLandmarkID
Indicates that a specific landmark is uniquely identified as being located within a particular 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.
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_69ca84e6493081909cf58c8d42ea856b |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb39719288190adf45e7c029edd51 |
completed | April 2, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69cd1d7621d48190aa6a6f34399514b0 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:35 p.m.