Triple
T1273145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Smith Tower |
E15753
|
entity |
| Predicate | mapFeature |
P7690
|
FINISHED |
| Object | landmark of downtown Seattle |
—
|
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: landmark of downtown Seattle | Statement: [Smith Tower, mapFeature, landmark of downtown Seattle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mapFeature Context triple: [Smith Tower, mapFeature, landmark of downtown Seattle]
-
A.
mapLabel
Indicates that a label or name is assigned to a map or mapped entity for identification or display.
-
B.
mapSymbol
Indicates a correspondence where one symbol is used to represent, stand for, or denote another element within a mapping or representation system.
-
C.
mapsFrom
Indicates that one entity is derived, transformed, or constructed based on data, structure, or content originating from another entity.
-
D.
featuresLocation
chosen
Indicates that something is characterized by or includes a specific location as one of its notable attributes.
-
E.
mapDesigner
Indicates that an entity is the designer or creator responsible for producing a particular map.
- 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_69a4935a94308190bb92555b79032824 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4c31602b8819087a57e8d390cae7a |
completed | March 1, 2026, 10:52 p.m. |
| PD | Predicate disambiguation | batch_69a4bee0be808190a8ccac6a41851fdd |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:50 p.m.