Triple
T34250112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gelsomina’s theme |
E878714
|
entity |
| Predicate | titleCharacterOrigin |
P34184
|
FINISHED |
| Object | Gelsomina from "La Strada" |
—
|
NE NERFINISHED |
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: Gelsomina from "La Strada" | Statement: [Gelsomina’s theme, titleCharacterOrigin, Gelsomina from "La Strada"]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleCharacterOrigin Context triple: [Gelsomina’s theme, titleCharacterOrigin, Gelsomina from "La Strada"]
-
A.
originOfCharacter
Indicates the source or place from which a character originates or is created.
-
B.
characterOrigin
chosen
Indicates the source, background, or initial context from which a character originates.
-
C.
basedOnCharacterOrigin
Indicates that one entity is derived from, inspired by, or determined according to the origin or background of a character.
-
D.
characterNameOrigin
Indicates the source or inspiration from which a character’s name is derived.
-
E.
protagonistOrigin
Indicates that one entity is the origin, source, or starting point of the protagonist in a narrative or story.
- 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_69f349b3618481909df955b063f305b2 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff2d22ffb48190ae58ddf3c7e02869 |
completed | May 9, 2026, 12:48 p.m. |
| PD | Predicate disambiguation | batch_69ff2ac2e1c4819096cc64e94aef2ff0 |
completed | May 9, 2026, 12:38 p.m. |
Created at: May 1, 2026, 1:56 a.m.