Triple
T21848260
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Triangulum–Andromeda overdensity |
E539432
|
entity |
| Predicate | hasEstimatedAge |
P122542
|
FINISHED |
| Object | several billion years |
—
|
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: several billion years | Statement: [Triangulum–Andromeda overdensity, hasEstimatedAge, several billion years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEstimatedAge Context triple: [Triangulum–Andromeda overdensity, hasEstimatedAge, several billion years]
-
A.
hasApproximateAgeRange
chosen
Indicates that one entity is associated with another entity representing an estimated or non-exact span of ages.
-
B.
approximateAgeBeforePresent
Indicates that one entity’s age is an estimated value measured as a time interval before the present moment.
-
C.
mayBeAgedIn
Indicates that an entity has the potential or option to undergo an aging or maturation process in a specified medium, container, or environment.
-
D.
hasRelativeAge
Indicates that one entity has an age that is defined or compared in relation to the age of another entity.
-
E.
containsAge
Indicates that one entity includes or specifies the age value or age-related information of another entity.
- 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_69e0c476c3c88190a92d08ebb59a128a |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f0bd56f4e081909a906b64c1019e6a |
completed | April 28, 2026, 1:59 p.m. |
| PD | Predicate disambiguation | batch_69e6be8c14748190bdcc44a14d50bea4 |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 6:55 p.m.