Triple
T6281832
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NADW |
E140798
|
entity |
| Predicate | densityDriver |
P69842
|
FINISHED |
| Object | low temperature |
—
|
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 temperature | Statement: [NADW, densityDriver, low temperature]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: densityDriver Context triple: [NADW, densityDriver, low temperature]
-
A.
possibleDriver
Indicates that an entity is a candidate or potential driver of another entity, such as a possible cause, regulator, or influencing factor.
-
B.
driverType
Indicates the category or role of a driver associated with an entity or activity (e.g., primary, backup, commercial, etc.).
-
C.
driveType
Indicates the type or configuration of the drive mechanism used to power or propel an entity.
-
D.
regulatoryDriver
Indicates that one entity serves as a motivating or guiding regulatory factor influencing the behavior, decisions, or policies of another entity.
-
E.
deploymentType
Indicates the manner or configuration in which a system, application, or component is deployed or made operational.
- 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_69c008cd17c8819082b82d3fbeb68047 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c063dee62881908347283f16dcbe68 |
completed | March 22, 2026, 9:49 p.m. |
| PD | Predicate disambiguation | batch_69c05608a5608190b22a1fdc4060470d |
completed | March 22, 2026, 8:50 p.m. |
| PDg | Predicate description generation | batch_69c05b37ac1881909e947822490ba4f2 |
completed | March 22, 2026, 9:12 p.m. |
Created at: March 22, 2026, 4:26 p.m.