Triple
T38372569
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Xavier |
E893528
|
entity |
| Predicate | hasImportanceInSeries |
P160849
|
FINISHED |
| Object | major 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: major character | Statement: [Xavier, hasImportanceInSeries, major character]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasImportanceInSeries Context triple: [Xavier, hasImportanceInSeries, major character]
-
A.
importanceToSeries
chosen
Indicates how crucial or significant an entity is within the context of a particular series.
-
B.
significantPlaceInSeries
Indicates that a place plays an important or notable role within the context of a particular series.
-
C.
basedInSeries
Indicates that one entity is set, located, or primarily takes place within the narrative world or context of a particular series.
-
D.
usedInSeries
Indicates that something (such as an element, component, or concept) is employed or appears within a particular series.
-
E.
importanceInSeason
Indicates the degree to which something is significant or influential within a specific season or seasonal context.
- 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_69f76e4b1f748190a380696a16eae4a2 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd3a69f1e08190a11aed015bff0858 |
completed | May 8, 2026, 1:20 a.m. |
| PD | Predicate disambiguation | batch_69fd39124180819080ca7911d3515d6d |
completed | May 8, 2026, 1:14 a.m. |
Created at: May 3, 2026, 4:31 p.m.