Triple
T4065654
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GOSAT |
E86316
|
entity |
| Predicate | dataApplication |
P399
|
FINISHED |
| Object | greenhouse gas emissions estimation |
—
|
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: greenhouse gas emissions estimation | Statement: [GOSAT, dataApplication, greenhouse gas emissions estimation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataApplication Context triple: [GOSAT, dataApplication, greenhouse gas emissions estimation]
-
A.
dataUse
chosen
Indicates how data is intended to be accessed, processed, or applied within a particular context or activity.
-
B.
typeOfApplication
Indicates the specific category or kind of application involved in the relationship or action.
-
C.
dataPortal
Indicates that an entity serves as or is associated with an online interface or gateway through which data can be accessed, managed, or distributed.
-
D.
dataInterface
Indicates that one entity serves as a data interface through which another entity can access, exchange, or manipulate data.
-
E.
notableApplicationDevelopedOn
Indicates that a notable software application was created or built to run on a particular platform, system, or technology.
- 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_69aed93c69208190a4efac0efe3cd69b |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefd0bdea48190805a79515ee92709 |
completed | March 9, 2026, 5:02 p.m. |
| PD | Predicate disambiguation | batch_69aef90438908190a005b08ba271eacf |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:38 p.m.