Triple
T3427450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elevation API |
E72257
|
entity |
| Predicate | responseField |
P48656
|
FINISHED |
| Object | elevation |
—
|
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: elevation | Statement: [Elevation API, responseField, elevation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: responseField Context triple: [Elevation API, responseField, elevation]
-
A.
responseFrom
Indicates that one entity is the originator or source of a response directed to another entity or request.
-
B.
responseFormula
Indicates that one entity’s reaction, reply, or outcome is expressed or encoded in a specific formula or structured representation.
-
C.
responseTool
Indicates a tool, method, or mechanism used to produce, deliver, or manage a response in a given context.
-
D.
typicalResponse
Indicates that an entity’s behavior, reaction, or outcome is the standard or commonly expected response in a given context or situation.
-
E.
supportsField
Indicates that one entity provides the necessary structure, stability, or backing for a particular field, area, or domain associated with another entity.
- 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_69ad85ae14308190bcbc25cfa0246c0b |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb982792c8190b1163eee4252210f |
completed | March 8, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_69adadfea024819094b41a13bc004bda |
completed | March 8, 2026, 5:12 p.m. |
| PDg | Predicate description generation | batch_69adb00f4f8c81908f88daf71f6a9c29 |
completed | March 8, 2026, 5:21 p.m. |
Created at: March 8, 2026, 3:15 p.m.