Triple
T30149597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nebraska Secretary of State |
E766358
|
entity |
| Predicate | officeLocatedInBuilding |
P166606
|
FINISHED |
| Object | Nebraska State Capitol |
—
|
NE NERFINISHED |
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: Nebraska State Capitol | Statement: [Nebraska Secretary of State, officeLocatedInBuilding, Nebraska State Capitol]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officeLocatedInBuilding Context triple: [Nebraska Secretary of State, officeLocatedInBuilding, Nebraska State Capitol]
-
A.
officeIsIn
Indicates that one office is located within or inside another specified place or building.
-
B.
isLocatedInBuilding
chosen
Indicates that one entity is physically situated within or inside the structure of a particular building.
-
C.
locatedOnBuilding
Indicates that one entity is physically situated on the exterior or rooftop surface of a building.
-
D.
locatedInBuildingOwnedBy
Indicates that one entity is situated within a building that is owned by another entity.
-
E.
locatedInBuildingUsedAs
Indicates that something is located inside a building that is being used for a specified purpose or function.
- 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_69f22479cd088190ab4c6f3fce39d1c5 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fe6c811bcc81908b1e1b1f8bcb071b |
completed | May 8, 2026, 11:06 p.m. |
| PD | Predicate disambiguation | batch_69fe6c026d5481908b7a814dcf38c183 |
completed | May 8, 2026, 11:04 p.m. |
Created at: April 29, 2026, 7:19 p.m.