Triple
T3524541
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ether |
E74505
|
entity |
| Predicate | roleInGas |
P49245
|
FINISHED |
| Object | unit of account for gas |
—
|
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: unit of account for gas | Statement: [Ether, roleInGas, unit of account for gas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInGas Context triple: [Ether, roleInGas, unit of account for gas]
-
A.
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.
-
B.
typeOfGasUsed
Indicates the specific kind of gas that is utilized in relation to an entity or process.
-
C.
gasContent
Indicates that one entity has, contains, or is characterized by a certain amount or type of gas.
-
D.
roleInEngine
Indicates the specific function or responsibility an entity has within an engine or engine-like system.
-
E.
roleInvolves
Indicates that a particular role includes or requires participation in a specified activity, responsibility, or function.
- 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_69ad85d0c5488190a3d8e02ebd01a1aa |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbc68b15881909b407486946ec3c5 |
completed | March 8, 2026, 6:14 p.m. |
| PD | Predicate disambiguation | batch_69adae121a048190b03825a001d21f49 |
completed | March 8, 2026, 5:12 p.m. |
| PDg | Predicate description generation | batch_69adb21a437c81908bca88d5e123d744 |
completed | March 8, 2026, 5:30 p.m. |
Created at: March 8, 2026, 3:19 p.m.