Triple
T18772825
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Population I |
E459057
|
entity |
| Predicate | characteristicAge |
P78532
|
FINISHED |
| Object | relatively young stars |
—
|
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: relatively young stars | Statement: [Population I, characteristicAge, relatively young stars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: characteristicAge Context triple: [Population I, characteristicAge, relatively young stars]
-
A.
characterAgeDescriptor
Indicates how a character’s age is qualitatively described or categorized (e.g., young, middle-aged, elderly) rather than given as a specific number.
-
B.
ageRecord
Indicates that there exists a record specifying the age of an entity at a particular time or in a particular context.
-
C.
riftAge
Indicates the age or time since formation of a geological rift or rift-related feature.
-
D.
typicalAge
chosen
Indicates the usual or characteristic age associated with an entity, event, or condition.
-
E.
ageModel
Indicates a relationship where one entity specifies or provides the age of another entity, typically in terms of a particular age value or age-related classification.
- 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_69d8d395dba0819087568404508590cb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e593378a4081909cc1b0856fce7d7d |
completed | April 20, 2026, 2:45 a.m. |
| PD | Predicate disambiguation | batch_69e48d1126e4819099607837ed5aadca |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:52 a.m.