Triple
T4780847
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Venera missions |
E106159
|
entity |
| Predicate | providedDataOn |
P17720
|
FINISHED |
| Object | Venusian atmospheric composition |
—
|
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: Venusian atmospheric composition | Statement: [Venera missions, providedDataOn, Venusian atmospheric composition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: providedDataOn Context triple: [Venera missions, providedDataOn, Venusian atmospheric composition]
-
A.
providedFor
Indicates that one entity supplies, furnishes, or makes something available to or on behalf of another entity for its use or benefit.
-
B.
providesInformationIn
chosen
Indicates that one entity supplies or conveys information within or through another entity or context.
-
C.
providedAt
Indicates that something is supplied, made available, or delivered at a specific time or location.
-
D.
collectsInformationOn
Indicates that one entity gathers or acquires data, facts, or details about another entity.
-
E.
providesThat
Indicates that one entity stipulates, specifies, or sets forth a condition, rule, or provision that applies to another entity or situation.
- 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_69bd43f3074c8190937e7b0a457fe9f1 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd69237f80819090713ed62653fb75 |
completed | March 20, 2026, 3:34 p.m. |
| PD | Predicate disambiguation | batch_69bd622be1388190ab5511b589c878c0 |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:21 p.m.