Triple
T405778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vaile Mansion |
E9379
|
entity |
| Predicate | localityRole |
P8234
|
FINISHED |
| Object | prominent local landmark in Independence, Missouri |
—
|
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: prominent local landmark in Independence, Missouri | Statement: [Vaile Mansion, localityRole, prominent local landmark in Independence, Missouri]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: localityRole Context triple: [Vaile Mansion, localityRole, prominent local landmark in Independence, Missouri]
-
A.
hasCityRole
chosen
Indicates that an entity holds or is assigned a specific role, function, or status within a particular city.
-
B.
representedLocallyBy
Indicates that an entity is expressed, implemented, or instantiated in a specific local form or representation by another entity.
-
C.
addressLocality
Indicates the city, town, or locality in which an address is situated.
-
D.
populationRole
Indicates the role or function that an entity has within a population or demographic context.
-
E.
modernLocality
Indicates that an entity is located in, associated with, or corresponds to a present-day geographic or administrative locality.
- 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_69a2e8004cb88190b92ed1add6abf41a |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2ecbc00508190bbb602179273f29c |
completed | Feb. 28, 2026, 1:25 p.m. |
| PD | Predicate disambiguation | batch_69a2e97066e8819083cc1b3a421b9650 |
completed | Feb. 28, 2026, 1:11 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.