Triple
T25804878
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clay Township, Boone County, Indiana |
E649940
|
entity |
| Predicate | hasUnitPreference |
P52348
|
FINISHED |
| Object | Imperial |
—
|
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: Imperial | Statement: [Clay Township, Boone County, Indiana, hasUnitPreference, Imperial]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUnitPreference Context triple: [Clay Township, Boone County, Indiana, hasUnitPreference, Imperial]
-
A.
hasUnitOf
Indicates that a quantity, measurement, or value is expressed in terms of a specific unit.
-
B.
unitPreference
chosen
Indicates a relationship where one entity specifies or favors a particular unit of measurement or representation over others.
-
C.
hasDistanceUnit
Indicates that a specified unit of measurement is used to express a distance value in the relationship.
-
D.
basedUnit
Indicates that one unit is defined in terms of, or derived from, another more fundamental unit.
-
E.
hasUnitFeature
Indicates that something possesses a specific unit-related characteristic or attribute, such as a measurable feature expressed in defined units.
- 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_69e7ab35d264819095367f7e80c983ff |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651a731508190bb0c8c2462eba224 |
completed | May 2, 2026, 7:33 p.m. |
Created at: April 22, 2026, 7:02 a.m.