Triple
T12800042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Young Acrobat |
E305991
|
entity |
| Predicate | protagonistSocialStatusAtStart |
P38113
|
FINISHED |
| Object | impoverished |
—
|
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: impoverished | Statement: [The Young Acrobat, protagonistSocialStatusAtStart, impoverished]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: protagonistSocialStatusAtStart Context triple: [The Young Acrobat, protagonistSocialStatusAtStart, impoverished]
-
A.
protagonistSocialStatus
Indicates the social standing or class position held by the story’s main character in relation to others in their society.
-
B.
protagonistStatusAtStart
chosen
Indicates the role or condition the main character is in at the beginning of the narrative or event.
-
C.
protagonistBackground
Indicates that one entity serves as the background, history, or prior circumstances of the protagonist entity in a narrative or story.
-
D.
protagonistDescription
Indicates that a text provides a descriptive summary or characterization of the story’s main protagonist.
-
E.
protagonistFamilyStatus
Indicates the familial role or position that a character holds in relation to the story’s protagonist.
- 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_69d7bdf366888190a8cccb982606889c |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96e7d3f5c8190bf01bef5d263ca26 |
completed | April 10, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69d9640ed7448190b276e7fab649f7d2 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:30 p.m.