Triple
T19686064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Milky Way globular cluster system |
E472714
|
entity |
| Predicate | hasTypicalAge |
P78532
|
FINISHED |
| Object | 10 to 13 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: 10 to 13 billion years | Statement: [Milky Way globular cluster system, hasTypicalAge, 10 to 13 billion years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalAge Context triple: [Milky Way globular cluster system, hasTypicalAge, 10 to 13 billion years]
-
A.
hasAge
Indicates that an entity possesses a specific age value, typically expressed as a number of time units since its birth or creation.
-
B.
typicalAge
chosen
Indicates the usual or characteristic age associated with an entity, event, or condition.
-
C.
containsAge
Indicates that one entity includes or specifies the age value or age-related information of another entity.
-
D.
hasLowerAge
Indicates that one entity is younger in age than another entity.
-
E.
canAgeFor
Indicates that one entity is capable of undergoing an aging or maturation process for the benefit, use, or context 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_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.