Triple
T10523573
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Latika |
E248235
|
entity |
| Predicate | hasAgeProgressionPortrayal |
P92996
|
FINISHED |
| Object | child |
—
|
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: child | Statement: [Latika, hasAgeProgressionPortrayal, child]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAgeProgressionPortrayal Context triple: [Latika, hasAgeProgressionPortrayal, child]
-
A.
ageProgression
Indicates a temporal relationship where an entity’s age increases or advances over time.
-
B.
ageProgressionDirection
chosen
Indicates the direction in which an entity’s age changes over time within a given process or representation (e.g., from younger to older or older to younger).
-
C.
hasAgeTransformation
Indicates a relationship where an entity undergoes or causes a change in age or age-related state.
-
D.
hasAge
Indicates that an entity possesses a specific age value, typically expressed as a number of time units since its birth or creation.
-
E.
hasAgeFocus
Indicates a relationship where something is characterized or distinguished by a particular age group or age-related emphasis.
- 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_69d381c5c7448190bec34bee7ec72bac |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d509e155b08190996325bf484ec55d |
completed | April 7, 2026, 1:42 p.m. |
| PD | Predicate disambiguation | batch_69d4fb94fa10819091f585bab4379c6f |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:29 p.m.