Triple
T29120917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Florina |
E737178
|
entity |
| Predicate | importanceInNovel |
P26062
|
FINISHED |
| Object | primary setting |
—
|
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: primary setting | Statement: [Florina, importanceInNovel, primary setting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: importanceInNovel Context triple: [Florina, importanceInNovel, primary setting]
-
A.
narrativeImportance
chosen
Indicates the degree to which an entity or event is central, influential, or essential within the structure and progression of a narrative.
-
B.
dramaticImportance
Indicates that one entity holds significant narrative or emotional weight or impact in relation to another within a dramatic or storytelling context.
-
C.
importanceInCanon
Indicates the degree to which something is considered significant or central within an established canon or official body of work.
-
D.
importanceInSeason
Indicates the degree to which something is significant or influential within a specific season or seasonal context.
-
E.
importanceToSeries
Indicates how crucial or significant an entity is within the context of a particular series.
- 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_69f077ed54e08190bb02a744e8121a66 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f69383222c81909d8baa04129d5c81 |
completed | May 3, 2026, 12:14 a.m. |
| PD | Predicate disambiguation | batch_69f690eb1e948190aab41a89969519a5 |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 28, 2026, 11:25 a.m.