Triple
T20295277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Devo Nod |
E505331
|
entity |
| Predicate | centralityInPlot |
P88311
|
FINISHED |
| Object | central character |
—
|
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: central character | Statement: [Devo Nod, centralityInPlot, central character]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centralityInPlot Context triple: [Devo Nod, centralityInPlot, central character]
-
A.
positionOnCentralization
Indicates the degree to which an entity favors centralized versus decentralized control, authority, or decision-making.
-
B.
primaryFunctionInPlot
chosen
Indicates the main narrative role or purpose that an entity serves within the plot of a story.
-
C.
isCentralTo
Indicates that something plays a primary, essential, or defining role in relation to something else, such that the latter depends on or is organized around it.
-
D.
centralPointSymbolizes
Indicates that a central point stands for, represents, or embodies a particular concept, value, or meaning within a given context.
-
E.
clusterConcentration
Indicates how densely the elements within a cluster are packed or distributed relative to one another.
- 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_69e0b4b8ab648190906e18538c250148 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6770714c4819080e3256325747ebf |
completed | April 20, 2026, 6:57 p.m. |
| PD | Predicate disambiguation | batch_69e55b21b09081909e46691b6f45a07f |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 16, 2026, 11:15 a.m.