Triple
T6430324
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hillary Step |
E128161
|
entity |
| Predicate | oxygenUseCommon |
P70856
|
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: [Hillary Step, oxygenUseCommon, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oxygenUseCommon Context triple: [Hillary Step, oxygenUseCommon, yes]
-
A.
oxygenValueApprox
Indicates that the oxygen value of an entity is approximately equal to a specified reference value, within an acceptable margin of error.
-
B.
oxygenRequirement
Indicates the level or type of oxygen needed by an entity to live, function, or operate.
-
C.
commonOn
Indicates that two or more entities share the same location, context, or medium where they are present or occur together.
-
D.
commonFor
Indicates that something is typical, usual, or frequently occurring for a given entity or context.
-
E.
widelyUsedIn
Indicates that something is commonly or extensively utilized within a particular context, domain, or group.
- 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_69c00838de888190af2eec0b80495efa |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0693b872c819082a7d0e257018831 |
completed | March 22, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69c060f780b08190aa650b4d1fc51f21 |
completed | March 22, 2026, 9:36 p.m. |
| PDg | Predicate description generation | batch_69c062d290448190a2183158ef75d129 |
completed | March 22, 2026, 9:44 p.m. |
Created at: March 22, 2026, 4:44 p.m.