Triple
T27968855
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Les Mystères du Nautilus |
E704799
|
entity |
| Predicate | primaryCharacterFeatured |
P9202
|
FINISHED |
| Object | Captain Nemo |
—
|
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: Captain Nemo | Statement: [Les Mystères du Nautilus, primaryCharacterFeatured, Captain Nemo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryCharacterFeatured Context triple: [Les Mystères du Nautilus, primaryCharacterFeatured, Captain Nemo]
-
A.
primaryActor
Indicates that the referenced entity is the main participant or most central party responsible for the action or event in the relationship.
-
B.
primaryCharacteristics
Indicates the main defining traits or features that most fundamentally characterize an entity.
-
C.
characterInFocus
Indicates that a particular character is the primary subject or focal point within a given context, scene, or narrative segment.
-
D.
protagonistCharacteristic
Indicates that a characteristic, trait, or defining quality is attributed to the protagonist in a narrative or scenario.
-
E.
mainProtagonist
chosen
Indicates that the subject is the central character or primary focus in the narrative of the related work.
- 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_69ef841061e48190b5570f9562f7434d |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69ffb97b8ff8819088b105d99a0820c9 |
completed | May 9, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69ffb88ef7388190a710120ed76edc0e |
completed | May 9, 2026, 10:43 p.m. |
Created at: April 27, 2026, 7:36 p.m.