Triple
T28795394
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cô Bé |
E727071
|
entity |
| Predicate | perceivedAge |
P161441
|
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: [Cô Bé, perceivedAge, child]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: perceivedAge Context triple: [Cô Bé, perceivedAge, child]
-
A.
relativeAgeInference
Indicates an inferred ordering of ages between entities, specifying which one is relatively older or younger based on available information.
-
B.
portrayalAge
chosen
Indicates the age or life stage at which an entity is depicted or represented in a given context.
-
C.
mayBeAgedIn
Indicates that an entity has the potential or option to undergo an aging or maturation process in a specified medium, container, or environment.
-
D.
portraysFromAge
Indicates that one entity depicts another entity starting from a specified age of the depicted entity.
-
E.
relativeAgeStatus
Indicates a comparative relationship specifying how the age of one entity relates to the age of another (e.g., older, younger, or same age).
- 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_69f0319b7c44819085736bcc256185e6 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec5bf508190ad088b89455252bd |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 28, 2026, 6:25 a.m.