Triple
T16336358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gaia Data Release 1 |
E396687
|
entity |
| Predicate | basedOnObservationsFrom |
P106874
|
FINISHED |
| Object | 2014-07 |
—
|
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: 2014-07 | Statement: [Gaia Data Release 1, basedOnObservationsFrom, 2014-07]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basedOnObservationsFrom Context triple: [Gaia Data Release 1, basedOnObservationsFrom, 2014-07]
-
A.
basedOnObservationOf
Indicates that something is derived from, justified by, or determined using a particular observation or set of observations.
-
B.
basedOnFactFrom
Indicates that something is derived, justified, or constructed using factual information obtained from a specified source.
-
C.
basedOnRecordingsFrom
chosen
Indicates that something is derived, constructed, or determined using information obtained from specific recordings.
-
D.
observedBy
Indicates that an entity is perceived, monitored, or recorded by another entity acting as the observer.
-
E.
observesFrom
Indicates that one entity watches, monitors, or takes note of another entity from a particular vantage point or location.
- 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_69d87f26864c819088365ca381a003c2 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2c4e3af7881908a3116c41ed69115 |
completed | April 17, 2026, 11:40 p.m. |
| PD | Predicate disambiguation | batch_69e226eba9b48190af6e80d3d1c2aed3 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:07 a.m.