Triple
T35676414
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vega |
E1030871
|
entity |
| Predicate | poleStarEpoch |
P183606
|
FINISHED |
| Object | around12000BC |
—
|
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: around12000BC | Statement: [Vega, poleStarEpoch, around12000BC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: poleStarEpoch Context triple: [Vega, poleStarEpoch, around12000BC]
-
A.
equatorialCoordinateEpoch
Indicates the specific reference date or epoch at which an object's equatorial coordinates (right ascension and declination) are defined or valid.
-
B.
poleStarOfSouthCelestialPole
Indicates the relationship in which a star serves as the pole star aligned with the south celestial pole.
-
C.
startDateSidereal
Indicates the sidereal (star-based) date on which an event, period, or state begins.
-
D.
endDateSidereal
Indicates the date and time, measured in sidereal rather than solar terms, at which a specified event, state, or interval comes to an end.
-
E.
starDate
Indicates a temporal relationship by assigning or associating a specific calendar or chronological date with an event, observation, or record.
- F. None of above. chosen
Provenance (4 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_69f76e0acfc0819082c8495c2210ce73 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a01efcc08190bba489a9099b8684 |
completed | May 3, 2026, 7:21 p.m. |
| PD | Predicate disambiguation | batch_69f79e4d885881908a3612e2e75cf84f |
completed | May 3, 2026, 7:13 p.m. |
| PDg | Predicate description generation | batch_69f79f477c4c8190a35cb6d87b1dcbd1 |
completed | May 3, 2026, 7:17 p.m. |
Created at: May 3, 2026, 4:05 p.m.