Triple
T19831525
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Perseus cloud complex |
E476470
|
entity |
| Predicate | hasGasTracer |
P62579
|
FINISHED |
| Object | carbon monoxide (CO) |
—
|
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: carbon monoxide (CO) | Statement: [Perseus cloud complex, hasGasTracer, carbon monoxide (CO)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGasTracer Context triple: [Perseus cloud complex, hasGasTracer, carbon monoxide (CO)]
-
A.
containsGasField
Indicates that one entity geographically includes or encompasses a gas field within its boundaries.
-
B.
hasPersistentGasEmissions
Indicates that an entity continuously or repeatedly releases gaseous substances over an extended period.
-
C.
usedAsTracerOf
chosen
Indicates that one entity is employed as a tracer to track, monitor, or follow the behavior, movement, or distribution of another entity.
-
D.
isGasRich
Indicates that an entity possesses a relatively high abundance or concentration of gas compared to a defined reference or threshold.
-
E.
isMoreGasRichThan
Indicates that one entity has a greater amount or proportion of gas than another entity.
- 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_69d8e51c7c188190b926f3a2a7b5f881 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e656ce68b48190aa25b29d0b6ea021 |
completed | April 20, 2026, 4:39 p.m. |
| PD | Predicate disambiguation | batch_69e5305bda388190a23b7191768107b1 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:50 p.m.