Triple
T13604830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Markleeville |
E325033
|
entity |
| Predicate | hasCountyGovernmentFunction |
P13896
|
FINISHED |
| Object | administrative center of Alpine 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: administrative center of Alpine County | Statement: [Markleeville, hasCountyGovernmentFunction, administrative center of Alpine County]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCountyGovernmentFunction Context triple: [Markleeville, hasCountyGovernmentFunction, administrative center of Alpine County]
-
A.
hasCountySeatFunction
chosen
Indicates that an entity serves as the official county seat, functioning as the administrative center for a county.
-
B.
hasCountyCouncil
Indicates that an entity is administratively governed or overseen by a specific county council.
-
C.
hasCountyAdministrator
Indicates that an entity is administered or overseen by a specific county administrator.
-
D.
hasCountyBoard
Indicates that an entity is governed, overseen, or administered by a specific county board.
-
E.
hasCountyGovernmentBuildings
Indicates that certain government buildings are administered or operated by a county-level authority.
- 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_69d80769eaf081909d82f44e484d6113 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbbb9ee3f081909056dc1a92c40b7a |
completed | April 12, 2026, 3:34 p.m. |
| PD | Predicate disambiguation | batch_69dbae1b3ee481909bd43ded6227a3e5 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:50 p.m.