Triple
T34660940
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enos |
E890103
|
entity |
| Predicate | featuresFictionalDeputy |
P23263
|
FINISHED |
| Object | Enos Strate |
E2107030
|
NE 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: Enos Strate | Statement: [Enos, featuresFictionalDeputy, Enos Strate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresFictionalDeputy Context triple: [Enos, featuresFictionalDeputy, Enos Strate]
-
A.
featuresCharacterWith
Indicates that one entity (such as a work or product) includes or presents a particular character as part of its content.
-
B.
featuresCharacterRole
chosen
Indicates that a work includes a character appearing in a specific narrative or functional role.
-
C.
fictionalCharacter
Indicates that one entity is a fictional character that appears within the narrative world of another entity (such as a work, series, or franchise).
-
D.
featuresFictionalUnit
Indicates that something includes or presents a fictional unit (such as a character, group, or organization) as part of its content or structure.
-
E.
fictionalCharacterFrom
Indicates that a fictional character originates from, or is created within, a particular work, universe, or source.
- F. None of above.
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_69f349d906bc8190b2efd9eff237d94b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a0357f9670081908a7ba1cd46a0b46a |
completed | May 12, 2026, 4:40 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a376f902cec81908cdecaa73b5246f6 |
completed | June 21, 2026, 4:58 a.m. |
| PD | Predicate disambiguation | batch_6a03575e3258819093303248d1569f95 |
completed | May 12, 2026, 4:37 p.m. |
Created at: May 1, 2026, 2:04 a.m.