Triple
T31136863
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tatum, New Mexico |
E793667
|
entity |
| Predicate | hasUtilities |
P124775
|
FINISHED |
| Object | electric service |
—
|
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: electric service | Statement: [Tatum, New Mexico, hasUtilities, electric service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUtilities Context triple: [Tatum, New Mexico, hasUtilities, electric service]
-
A.
hasMajorUtility
chosen
Indicates that an entity possesses or is served by a primary or significant utility service (such as power, water, or gas).
-
B.
hasUnitFeature
Indicates that something possesses a specific unit-related characteristic or attribute, such as a measurable feature expressed in defined units.
-
C.
typeOfUtility
Indicates that one entity is a specific kind or category of utility associated with another entity.
-
D.
hasUseCase
Indicates that one entity is employed, applied, or utilized as a solution or method to address a particular need, problem, or scenario associated with another entity.
-
E.
hasCap
Indicates that an entity possesses or is equipped with a cap or top covering.
- 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_69f224d2b3a48190aa9dd26fbf6eab1a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69c234d648190a243fb2b107136a9 |
completed | May 3, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69f69665cd9c819088c388fc82fec42e |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 9:05 p.m.