Triple
T16566396
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gaia Early Data Release 3 |
E402472
|
entity |
| Predicate | dataCollectionPeriodStart |
P45301
|
FINISHED |
| Object | 2014-07-25 |
—
|
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-25 | Statement: [Gaia Early Data Release 3, dataCollectionPeriodStart, 2014-07-25]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataCollectionPeriodStart Context triple: [Gaia Early Data Release 3, dataCollectionPeriodStart, 2014-07-25]
-
A.
startDateOfCollection
chosen
Indicates the calendar date on which a particular collection or collecting activity begins.
-
B.
typicalCollectionPeriodStart
Indicates the date or point in time when a standard or customary collection period begins.
-
C.
recordedInPeriodStart
Indicates that an event or record began or was first documented at the start of a specified time period.
-
D.
dataCollectedOn
Indicates that certain data was gathered, recorded, or measured at a specific point in time or on a particular date.
-
E.
usePeriodStart
Indicates that an entity begins to be used or becomes active starting from a specified time period.
- 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_69d8838648088190acf97ef11fc3f61b |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e35772255881909f737da89bcd06b8 |
completed | April 18, 2026, 10:05 a.m. |
| PD | Predicate disambiguation | batch_69e296a47b7481909d9958158510c806 |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:15 a.m.