Triple
T31750245
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chachi people |
E810395
|
entity |
| Predicate | elevationOfHouses |
P221
|
FINISHED |
| Object | raised above ground |
—
|
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: raised above ground | Statement: [Chachi people, elevationOfHouses, raised above ground]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: elevationOfHouses Context triple: [Chachi people, elevationOfHouses, raised above ground]
-
A.
hasFloorElevation
Indicates that one entity has a specified vertical height or level above a reference point (such as sea level or ground) for its floor.
-
B.
elevationAboveTown
Indicates that one location is situated at a higher elevation relative to a specified town.
-
C.
elevation
chosen
Indicates the vertical height or altitude of one entity relative to a reference level or another entity.
-
D.
elevationAboveStreet
Indicates the vertical height difference of something relative to the level of the adjacent street.
-
E.
elevationApproxMeters
Indicates the approximate elevation of an entity above sea level, measured in meters.
- 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_69f348e233cc819083b6695f70cd75d8 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f73223675481908c1bc3208c0f5284 |
completed | May 3, 2026, 11:31 a.m. |
| PD | Predicate disambiguation | batch_69f7317690108190b3aae2cd2e1d069e |
completed | May 3, 2026, 11:28 a.m. |
Created at: April 30, 2026, 11:27 p.m.