Triple
T19686063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Milky Way globular cluster system |
E472714
|
entity |
| Predicate | hasOldestAges |
P92699
|
FINISHED |
| Object | greater than 12 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: greater than 12 billion years | Statement: [Milky Way globular cluster system, hasOldestAges, greater than 12 billion years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOldestAges Context triple: [Milky Way globular cluster system, hasOldestAges, greater than 12 billion years]
-
A.
oldestAge
chosen
Indicates that the associated value represents the greatest (maximum) age within a given group, set, or context.
-
B.
isOldest
Indicates that one entity has a greater age than all other relevant entities in the comparison set.
-
C.
containsAge
Indicates that one entity includes or specifies the age value or age-related information of another entity.
-
D.
hasElders
Indicates that one entity has elders, i.e., individuals recognized as senior, guiding, or authoritative figures in relation to it.
-
E.
numberOfAges
Indicates the count of distinct ages associated with an entity or within a specified group or context.
- 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_69d8e515bef88190bc30781aea50537a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6420c3f50819082b64b1fa4335e56 |
completed | April 20, 2026, 3:11 p.m. |
| PD | Predicate disambiguation | batch_69e53039ea808190a9106a53f564ab92 |
completed | April 19, 2026, 7:42 p.m. |
Created at: April 10, 2026, 1:45 p.m.