Triple
T28156043
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anna Beam |
E714749
|
entity |
| Predicate | hasAgeInDepictedEvents |
P94404
|
FINISHED |
| Object | approximately 10 years old |
—
|
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: approximately 10 years old | Statement: [Anna Beam, hasAgeInDepictedEvents, approximately 10 years old]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAgeInDepictedEvents Context triple: [Anna Beam, hasAgeInDepictedEvents, approximately 10 years old]
-
A.
ageDuringMainEvents
chosen
Indicates the age an entity has at the time when the main events of a referenced context or narrative occur.
-
B.
hasAgeParticipation
Indicates a relationship where an entity’s participation or involvement is characterized or constrained by a specific age or age range.
-
C.
hasAgeSignificance
Indicates that something holds particular importance, relevance, or meaning specifically due to its age or the age of an associated entity.
-
D.
hasHistoricEventYear
Indicates the specific year in which a referenced historic event took place.
-
E.
hasHistoricalEvent
Indicates that a historical event occurred in, is associated with, or is relevant to a particular 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_69efd6b156448190bfa15958208395c3 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f641e787b0819098a5fc8c645c9c46 |
completed | May 2, 2026, 6:26 p.m. |
| PD | Predicate disambiguation | batch_69f63c6a8474819091b8c6fe98e3862d |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 10:02 p.m.