Triple
T3949850
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Major Oak |
E84837
|
entity |
| Predicate | estimatedAgeInYears |
P2042
|
FINISHED |
| Object | about 800 |
—
|
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: about 800 | Statement: [Major Oak, estimatedAgeInYears, about 800]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: estimatedAgeInYears Context triple: [Major Oak, estimatedAgeInYears, about 800]
-
A.
containsAge
Indicates that one entity includes or specifies the age value or age-related information of another entity.
-
B.
hasAge
chosen
Indicates that an entity possesses a specific age value, typically expressed as a number of time units since its birth or creation.
-
C.
estimatedAgeInMillionsOfYears
Indicates the approximate age of something expressed in units of millions of years.
-
D.
ageStatus
Indicates the relationship between an entity and its classification into an age-related category or status (e.g., minor, adult, senior).
-
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_69aed934fbfc8190847068e4546de963 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefaa5afdc8190b709af2473d75d02 |
completed | March 9, 2026, 4:51 p.m. |
| PD | Predicate disambiguation | batch_69aef8ed04e4819096bced8971cd888d |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:30 p.m.