Triple
T36954229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Merchant Alliance |
E914147
|
entity |
| Predicate | emissaryFlagEffect |
P164814
|
FINISHED |
| Object | increased rewards |
—
|
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: increased rewards | Statement: [Merchant Alliance, emissaryFlagEffect, increased rewards]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: emissaryFlagEffect Context triple: [Merchant Alliance, emissaryFlagEffect, increased rewards]
-
A.
effectOnFlags
chosen
Indicates how an action or event changes, sets, or influences the state of one or more flags.
-
B.
flagElement
Indicates that one entity serves as a flag or marker element associated with another entity, typically used to signal a condition, state, or special handling.
-
C.
flagshipFor
Indicates that one entity serves as the primary or leading representative example for another entity, often embodying its most important qualities or status.
-
D.
flagshipDuringBattle
Indicates that one entity serves as the primary command ship for another entity during a specific battle or military engagement.
-
E.
isOnFlagOf
Indicates that something (typically a symbol, image, or design element) appears on or is depicted on a flag.
- 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_69f76e8b28848190abd81fe7a7374910 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fba2877b248190a974eb092243c0c4 |
completed | May 6, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69fb8d06a1b48190a937aa410d159dfa |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:13 p.m.