Triple
T11022964
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jem Finch |
E260537
|
entity |
| Predicate | fictionalAgeRange |
P96629
|
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: [Jem Finch, fictionalAgeRange, child]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fictionalAgeRange Context triple: [Jem Finch, fictionalAgeRange, child]
-
A.
fictionalAge
Indicates the age attributed to an entity within a fictional or narrative context, rather than its real-world age.
-
B.
fictionalEra
Indicates the time period or age within a fictional or imaginary setting in which an entity exists or an event occurs.
-
C.
fictionalBirthYear
Indicates the year in which a fictional character is stated or assumed to have been born within its narrative or canon.
-
D.
fictionalOrigin
Indicates that one entity originates from, or was first introduced within, a fictional work, universe, or narrative created by another entity.
-
E.
fictionalTime
Indicates that the associated time or temporal reference exists only within a fictional or imagined context, rather than in real-world chronology.
- F. None of above. chosen
Provenance (4 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_69d6aa9687448190b28d353b1b6a610e |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d797bd88188190a644adc9283cabb8 |
completed | April 9, 2026, 12:12 p.m. |
| PD | Predicate disambiguation | batch_69d72e995e008190bbffb314129ed0cd |
completed | April 9, 2026, 4:44 a.m. |
| PDg | Predicate description generation | batch_69d732242fdc8190be77d1f730a42935 |
completed | April 9, 2026, 4:59 a.m. |
Created at: April 8, 2026, 9:25 p.m.