Triple
T34931090
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Independence SuperChair |
E1007435
|
entity |
| Predicate | servesTerrainOn |
P106961
|
FINISHED |
| Object | Peak 7 |
—
|
NE NERFINISHED |
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: Peak 7 | Statement: [Independence SuperChair, servesTerrainOn, Peak 7]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesTerrainOn Context triple: [Independence SuperChair, servesTerrainOn, Peak 7]
-
A.
locatedOnTerrain
Indicates that one entity is physically situated on or atop a particular terrain surface.
-
B.
hasTerrainFor
chosen
Indicates that a location or area possesses terrain suitable or designated for a particular use, activity, or feature.
-
C.
involvesTerrain
Indicates that the relationship or action takes place in, across, or is directly affected by a specified type of terrain or landform.
-
D.
servesOn
Indicates that one entity performs duties, functions, or holds a role as a member within another entity, such as a group, body, or organization.
-
E.
hasGeneralTerrain
Indicates that an entity is characterized by or associated with a particular overall type of terrain.
- 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_69f76dc3d83881909d5c3c14455cfa2c |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ffe6e2eb688190a45fd2c6415cd86a |
completed | May 10, 2026, 2:01 a.m. |
| PD | Predicate disambiguation | batch_69ffe65939488190a35b9c2e9c7ad868 |
completed | May 10, 2026, 1:58 a.m. |
Created at: May 3, 2026, 4 p.m.