Triple
T28601456
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cheviot Hills Golf Course |
E723922
|
entity |
| Predicate | municipalCourse |
P46349
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Cheviot Hills Golf Course, municipalCourse, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: municipalCourse Context triple: [Cheviot Hills Golf Course, municipalCourse, true]
-
A.
municipalScope
Indicates that something falls within the authority, jurisdiction, or functional domain of a municipality or local city government.
-
B.
municipality
Indicates that one entity is a municipality (a local administrative unit) in which the other entity is located or which it governs.
-
C.
municipalIntegration
Indicates the incorporation or coordination of local governmental functions, services, or jurisdictions into a unified municipal framework.
-
D.
municipalKey
Indicates a unique identifier that links an entity to a specific municipality within an administrative or geographic system.
-
E.
isMunicipal
chosen
Indicates that something belongs to, is administered by, or is characteristic of a municipality or local city government.
- 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_69f01d80b1908190980594837604b8c7 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b78f29481908cc8f390496dee97 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 28, 2026, 4:24 a.m.