Triple
T25855171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carson City, Nevada |
E651322
|
entity |
| Predicate | hasJudicialBuilding |
P7595
|
FINISHED |
| Object | Nevada Supreme Court building |
—
|
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: Nevada Supreme Court building | Statement: [Carson City, Nevada, hasJudicialBuilding, Nevada Supreme Court building]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasJudicialBuilding Context triple: [Carson City, Nevada, hasJudicialBuilding, Nevada Supreme Court building]
-
A.
hasCourthouse
chosen
Indicates that a location or jurisdiction possesses or contains a courthouse.
-
B.
hasJudicialHeadquarters
Indicates that a judicial body or system is officially based or headquartered at a specific location.
-
C.
hasJudicialSeat
Indicates that an entity holds an official position or seat within a judicial body or court.
-
D.
hasLegislatureBuilding
Indicates that one entity serves as the official legislature building or physical premises where the legislative body of another entity meets or operates.
-
E.
hasJudiciary
Indicates that an entity possesses, is served by, or is under the authority of a judicial body or legal court system.
- 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_69e7ab39035c8190be15c8aaee1bb858 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f602671f8c819080ee83a2c2b1ed2f |
completed | May 2, 2026, 1:55 p.m. |
| PD | Predicate disambiguation | batch_69f4a0fed15881909b789251fe5d8d45 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 22, 2026, 8 a.m.