Triple
T32117719
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viltrumite |
E820281
|
entity |
| Predicate | agingPattern |
P8034
|
FINISHED |
| Object | age slowly after reaching maturity |
—
|
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: age slowly after reaching maturity | Statement: [Viltrumite, agingPattern, age slowly after reaching maturity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: agingPattern Context triple: [Viltrumite, agingPattern, age slowly after reaching maturity]
-
A.
agingCommon
Indicates that the entities share a common or typical pattern, process, or characteristic related to aging.
-
B.
agingMethod
Indicates the process or technique by which something (typically a product or material) is matured, aged, or allowed to develop its characteristics over time.
-
C.
pattern
chosen
Indicates that one entity exhibits, follows, or is characterized by a particular recurring form, structure, or arrangement associated with another entity.
-
D.
agingCategory
Indicates the classification of an entity based on its stage or degree of aging.
-
E.
agingPractice
Indicates a relationship where an entity engages in or applies methods, behaviors, or techniques related to the process or management of aging.
- 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_69f3490209c881908ec0241476715f15 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b909e534819085361d443b5c622d |
completed | May 3, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a970b0819090c6473844ffa8e3 |
completed | May 3, 2026, 2:32 a.m. |
Created at: May 1, 2026, 12:28 a.m.