Triple
T14569029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LZ 1 |
E341862
|
entity |
| Predicate | gasCellType |
P3601
|
FINISHED |
| Object | multiple internal gas cells |
—
|
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: multiple internal gas cells | Statement: [LZ 1, gasCellType, multiple internal gas cells]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gasCellType Context triple: [LZ 1, gasCellType, multiple internal gas cells]
-
A.
cellType
chosen
Indicates the classification relationship that specifies what type of cell an entity is or is associated with.
-
B.
gasContent
Indicates that one entity has, contains, or is characterized by a certain amount or type of gas.
-
C.
cellTypeUsed
Indicates that a particular type of cell is employed or utilized in relation to another entity or process.
-
D.
gasSystem
Indicates a relationship where an entity functions as, is part of, or is associated with a gas-based system used for distribution, control, or processing of gases.
-
E.
typeOfGasUsed
Indicates the specific kind of gas that is utilized in relation to an entity or process.
- 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_69d822dcc6248190bed689984bceb0e2 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb3f2121481908f2385637944785d |
completed | April 14, 2026, 9:38 p.m. |
| PD | Predicate disambiguation | batch_69de5c57489c8190b57917be1dba6ae6 |
completed | April 14, 2026, 3:25 p.m. |
Created at: April 10, 2026, 1:23 a.m.