Triple
T1273136
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Smith Tower |
E15753
|
entity |
| Predicate | addedToRegister |
P4097
|
FINISHED |
| Object | Seattle Landmarks Preservation Board list |
—
|
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 Landmarks Preservation Board list | Statement: [Smith Tower, addedToRegister, Seattle Landmarks Preservation Board list]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addedToRegister Context triple: [Smith Tower, addedToRegister, Seattle Landmarks Preservation Board list]
-
A.
addedTo
chosen
Indicates that one entity has been included or incorporated into another entity, typically as a new component, member, or element.
-
B.
hasRegister
Indicates that one entity possesses, contains, or is associated with a specific register (such as a record, log, or hardware register).
-
C.
registrationEffect
Indicates the outcome or consequence that results from an entity being registered or from the act of registration taking place.
-
D.
attachedTo
Indicates that one entity is physically or logically fastened, connected, or joined to another entity.
-
E.
register
Indicates that an entity formally records or enrolls another entity or itself in an official system, list, or record.
- 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.