Triple
T9756923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unit 1 |
E236575
|
entity |
| Predicate | hasReactorVessel |
P26083
|
FINISHED |
| Object | steel pressure vessel |
—
|
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: steel pressure vessel | Statement: [Unit 1, hasReactorVessel, steel pressure vessel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReactorVessel Context triple: [Unit 1, hasReactorVessel, steel pressure vessel]
-
A.
hasReactorUnit
Indicates that one entity possesses, contains, or is equipped with a specific reactor unit as a component or subsystem.
-
B.
hasVessel
chosen
Indicates that one entity possesses, uses, or is associated with a particular vessel (such as a container, ship, or transport medium) in the context of the described relationship or action.
-
C.
reactorType
Indicates the specific kind or category of reactor associated with an entity.
-
D.
hasReactorVendor
Indicates that one entity serves as the supplier or manufacturer of a reactor for another entity.
-
E.
possibleFermentationVessel
Indicates that something can serve as a suitable container or environment in which fermentation may take place.
- 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_69ca84d64f6c8190a4ed4e9f5936eda5 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9fb2889481908fba4a449d5007fe |
completed | April 1, 2026, 10:44 p.m. |
| PD | Predicate disambiguation | batch_69cd03d0772c8190bd1750cf1cfba309 |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:24 p.m.