Triple
T24576061
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hastings Museum of Natural and Cultural History |
E608108
|
entity |
| Predicate | stateWhereLocated |
P96807
|
FINISHED |
| Object | Nebraska |
—
|
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 | Statement: [Hastings Museum of Natural and Cultural History, stateWhereLocated, Nebraska]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stateWhereLocated Context triple: [Hastings Museum of Natural and Cultural History, stateWhereLocated, Nebraska]
-
A.
locatedInStateOrRegion
chosen
Indicates that one entity is geographically situated within the boundaries of a specified state or region.
-
B.
countryLocated
Indicates that a country is geographically situated within or associated with a specific larger region, territory, or political entity.
-
C.
timeLocatedIn
Indicates that an event, state, or entity occurs, exists, or is valid within a specified time or temporal interval.
-
D.
locatedIn
Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of another entity.
-
E.
regionSeatLocatedIn
Indicates that the administrative seat or capital of a region is located within that region.
- 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_69e2c4cdab6c8190aae6e5d3de55c95e |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a9295ab08190b6c137c99bcd958f |
completed | April 30, 2026, 12:58 a.m. |
| PD | Predicate disambiguation | batch_69f2a6c1f07081908edf0b521767e79b |
completed | April 30, 2026, 12:48 a.m. |
Created at: April 18, 2026, 2:29 a.m.