Triple
T29139634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | High Charity |
E738588
|
entity |
| Predicate | enemyFactionControl |
P99416
|
FINISHED |
| Object | Flood (after infestation) |
—
|
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: Flood (after infestation) | Statement: [High Charity, enemyFactionControl, Flood (after infestation)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enemyFactionControl Context triple: [High Charity, enemyFactionControl, Flood (after infestation)]
-
A.
hasOpposingFaction
Indicates that one faction stands in opposition or conflict to another faction.
-
B.
enemyOrganization
Indicates that one organization is considered an adversary or opponent of another organization, typically in a hostile or competitive context.
-
C.
enemyForceType
chosen
Indicates that one entity is characterized as a hostile or opposing force of a specified type relative to another entity.
-
D.
enemyNation
Indicates that one nation is considered a hostile or adversarial state in relation to another nation.
-
E.
enemyTribe
Indicates that one tribe is in an adversarial or hostile relationship with another tribe.
- 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_69f07cb3adb48190a9e0e169cd026634 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f6691f5e188190b12c7b2eb729a45e |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f6659b62fc8190b21555d0ba54db2d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 11:35 a.m.