Triple
T38014268
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Rout of the White Hussars |
E948448
|
entity |
| Predicate | hasFictionalUnit |
P15645
|
FINISHED |
| Object | White Hussars |
—
|
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: White Hussars | Statement: [The Rout of the White Hussars, hasFictionalUnit, White Hussars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFictionalUnit Context triple: [The Rout of the White Hussars, hasFictionalUnit, White Hussars]
-
A.
hasFictionalUniverseElement
chosen
Indicates that one entity is a component, feature, or constituent part of the fictional universe represented by the other entity.
-
B.
hasFictionalForm
Indicates that an entity has a counterpart or representation that exists within a fictional or imaginary context.
-
C.
hasFictionalType
Indicates that an entity is associated with or classified under a particular type or category that is fictional rather than real.
-
D.
hasFictionalScope
Indicates that something pertains to, applies within, or is limited to a fictional or imagined context rather than real-world scope.
-
E.
hasFictionalFunction
Indicates that an entity serves a role, purpose, or function within a fictional context or narrative.
- 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_69f76efc10448190aff5fb566b98f952 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a0079e152648190a9da2add94fc1831 |
completed | May 10, 2026, 12:28 p.m. |
| PD | Predicate disambiguation | batch_6a0078f77f9c8190af357a6016a2bd53 |
completed | May 10, 2026, 12:24 p.m. |
Created at: May 3, 2026, 4:20 p.m.