Triple
T32713208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iten |
E836451
|
entity |
| Predicate | airDensityCondition |
P116442
|
FINISHED |
| Object | low air density beneficial for endurance training |
—
|
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: low air density beneficial for endurance training | Statement: [Iten, airDensityCondition, low air density beneficial for endurance training]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: airDensityCondition Context triple: [Iten, airDensityCondition, low air density beneficial for endurance training]
-
A.
atmosphereStatus
chosen
Indicates the current condition or state of an atmosphere, such as its composition, quality, or environmental status.
-
B.
temperatureConditions
Indicates the specific thermal or weather-related temperature state or range affecting an entity or situation.
-
C.
isAirSensitive
Indicates that the subject undergoes degradation, reaction, or loss of function upon exposure to air.
-
D.
hasAirConditioning
Indicates that an entity is equipped with or provides air conditioning.
-
E.
typicalPressure
Indicates the usual or characteristic level of pressure typically associated with an entity, situation, or condition.
- 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_69f3493446148190819541f3ffe79975 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6c883541c8190abff705a5658bc68 |
completed | May 3, 2026, 4:01 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f617c08190a70ba880210f908c |
completed | May 3, 2026, 3:41 a.m. |
Created at: May 1, 2026, 1:11 a.m.