Triple
T33914271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ursa |
E869406
|
entity |
| Predicate | fightsOnSideOf |
P126844
|
FINISHED |
| Object | Kryptonian criminals |
—
|
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: Kryptonian criminals | Statement: [Ursa, fightsOnSideOf, Kryptonian criminals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fightsOnSideOf Context triple: [Ursa, fightsOnSideOf, Kryptonian criminals]
-
A.
conflictSide
Indicates that an entity participates as a distinct party or faction on one side of a conflict or dispute.
-
B.
foughtForFaction
chosen
Indicates that an entity actively participated in or supported a particular faction, typically in a conflict or struggle.
-
C.
foughtAs
Indicates that an entity participated in a conflict or war in the capacity, role, or identity specified by another entity.
-
D.
partySide
Indicates the role or alignment a participant has within a conflict, agreement, or legal case (e.g., plaintiff vs. defendant, or one side vs. the opposing side).
-
E.
hasOpposingFaction
Indicates that one faction stands in opposition or conflict to another faction.
- 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_69f3499869bc8190b6c33a81686af226 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7051ad6e4819095e82bbd64761803 |
completed | May 3, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69f700fe24e08190998e2c96fbaaad38 |
completed | May 3, 2026, 8:02 a.m. |
Created at: May 1, 2026, 1:48 a.m.