Triple
T12717078
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | INSAT-3DR |
E303872
|
entity |
| Predicate | dataRelayFunction |
P37199
|
FINISHED |
| Object | meteorological data collection platforms |
—
|
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: meteorological data collection platforms | Statement: [INSAT-3DR, dataRelayFunction, meteorological data collection platforms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataRelayFunction Context triple: [INSAT-3DR, dataRelayFunction, meteorological data collection platforms]
-
A.
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.
-
B.
dataInterface
chosen
Indicates that one entity serves as a data interface through which another entity can access, exchange, or manipulate data.
-
C.
dataControl
Indicates that one entity has the authority or capability to determine how another entity’s data is collected, used, shared, or managed.
-
D.
dataModel
Indicates a relationship where an entity defines, uses, or is structured according to a specific data model or schema.
-
E.
dataContext
Indicates the situational or environmental conditions under which data is produced, interpreted, or used, such as source, scope, assumptions, and relevant constraints.
- 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_69d7bdf084148190ab9d513dc0735af4 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9620bd6148190a2f50067a4c18c14 |
completed | April 10, 2026, 8:48 p.m. |
| PD | Predicate disambiguation | batch_69d960c088dc8190b0e63312c54e4c6c |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:23 p.m.