Triple
T27046163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Washington County, Indiana |
E684636
|
entity |
| Predicate | hasRollingHills |
P174674
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Washington County, Indiana, hasRollingHills, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRollingHills Context triple: [Washington County, Indiana, hasRollingHills, yes]
-
A.
containsHill
Indicates that one entity geographically includes or encompasses a hill within its area or boundaries.
-
B.
hasApproximateNumberOfHills
Indicates that an entity is associated with an estimated or imprecise count of hills rather than an exact number.
-
C.
hasNearbyHills
Indicates that one location or area is situated close to one or more hills.
-
D.
isHill
Indicates that the subject entity is classified as a hill, i.e., a naturally raised area of land lower and less steep than a mountain.
-
E.
isOnHill
Indicates that one entity is located on or atop a hill relative to another reference frame or context.
- F. None of above. chosen
Provenance (4 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_69ef148193c48190bb1a0cfae6a407c4 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f6c5b7e46081909975b05f7298cc0e |
completed | May 3, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f23ae081909a52801266063a3c |
completed | May 3, 2026, 3:41 a.m. |
| PDg | Predicate description generation | batch_69f6c49069e48190a3486b6254a6645b |
completed | May 3, 2026, 3:44 a.m. |
Created at: April 27, 2026, 8:10 a.m.