Triple
T8712071
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aqua-Lung |
E206799
|
entity |
| Predicate | pressureStageCount |
P7615
|
FINISHED |
| Object | two-stage regulator |
—
|
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: two-stage regulator | Statement: [Aqua-Lung, pressureStageCount, two-stage regulator]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pressureStageCount Context triple: [Aqua-Lung, pressureStageCount, two-stage regulator]
-
A.
numberOfStages
chosen
Indicates the total count of distinct stages or phases associated with a given process, event, or entity.
-
B.
pressureCapability
Indicates the maximum pressure an entity can safely exert, withstand, or operate under within a given context.
-
C.
stages
Indicates that one entity organizes, presents, or sets up another entity (such as an event, performance, or situation) to take place or be displayed.
-
D.
stageOf
Indicates that one entity represents a particular phase, step, or developmental period within the progression or lifecycle of another entity.
-
E.
pressureType
Indicates the specific category or kind of pressure associated with an entity or interaction.
- 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_69ca83572d4881909bef3be2b578d539 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5c32aebc8190ba19299ce9a18efd |
completed | March 31, 2026, 11:43 p.m. |
| PD | Predicate disambiguation | batch_69cc456e806c819087e7d66ee737f242 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:35 p.m.