Triple
T817556
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carson City |
E17682
|
entity |
| Predicate | countyStatus |
P4809
|
FINISHED |
| Object | independent of any county |
—
|
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: independent of any county | Statement: [Carson City, countyStatus, independent of any county]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: countyStatus Context triple: [Carson City, countyStatus, independent of any county]
-
A.
nationalRegisterStatus
Indicates whether an entity is listed, eligible, or otherwise classified within an official national register or registry.
-
B.
statusInUnitedStates
Indicates the legal or official standing that an entity holds within the jurisdiction of the United States.
-
C.
stateRock
Indicates that an entity is in a solid, rock-like physical state or condition.
-
D.
countryStatus
Indicates the political or legal condition of a country, such as its sovereignty, recognition, or current state in international or domestic contexts.
-
E.
territorialStatus
chosen
Indicates the legal or political condition of control, sovereignty, or jurisdiction that applies to a specific territory.
- 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_69a4937bcaac8190a322524ac6f45a5a |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4ab976094819086d676404d745750 |
completed | March 1, 2026, 9:11 p.m. |
| PD | Predicate disambiguation | batch_69a4aa76a7808190ac7fd9ba1a4cebcb |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:38 p.m.