Triple
T34976009
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Krakozhia |
E1008677
|
entity |
| Predicate | hasFictionalMilitary |
P33843
|
FINISHED |
| Object | Krakozhian military |
—
|
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: Krakozhian military | Statement: [Krakozhia, hasFictionalMilitary, Krakozhian military]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFictionalMilitary Context triple: [Krakozhia, hasFictionalMilitary, Krakozhian military]
-
A.
hasFictionalWar
Indicates that there exists a fictional or imagined war involving the related entities.
-
B.
hasFictionalDepictions
Indicates that an entity is represented or portrayed in one or more fictional works or narratives.
-
C.
warServedInFictionally
Indicates that a fictional character is depicted as having served in a particular war within a narrative or story.
-
D.
hasFictionalContent
Indicates that something contains or includes material that is imaginary, invented, or not intended to represent real events or facts.
-
E.
hasFictionalForm
chosen
Indicates that an entity has a counterpart or representation that exists within a fictional or imaginary 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_69f76dc78a308190a1ac29ad4a9a4895 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ffab5adf2c819084700c5ea34615bf |
completed | May 9, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69ffaabffa208190b5214ca17cc8a5ea |
completed | May 9, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:01 p.m.