Triple
T33462112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joseph Rouletabille series |
E856945
|
entity |
| Predicate | hasProtagonistNameOrigin |
P148817
|
FINISHED |
| Object | French literature |
—
|
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: French literature | Statement: [Joseph Rouletabille series, hasProtagonistNameOrigin, French literature]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProtagonistNameOrigin Context triple: [Joseph Rouletabille series, hasProtagonistNameOrigin, French literature]
-
A.
characterNameOrigin
chosen
Indicates the source or inspiration from which a character’s name is derived.
-
B.
protagonistOrigin
Indicates that one entity is the origin, source, or starting point of the protagonist in a narrative or story.
-
C.
hasNameOrigin
Indicates that the origin or source of an entity’s name is specified by the related entity.
-
D.
hasOriginalCharacterName
Indicates that an entity is associated with its initial or primary character name before any changes or adaptations.
-
E.
characterOrigin
Indicates the source, background, or initial context from which a character originates.
- 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_69f34973461481909c701c98ebd75623 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a019d1407588190b3b9b83fca2e61fe |
completed | May 11, 2026, 9:10 a.m. |
| PD | Predicate disambiguation | batch_6a019c760e3081909cfe9c0603727e48 |
completed | May 11, 2026, 9:08 a.m. |
Created at: May 1, 2026, 1:37 a.m.