Triple
T36954228
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Merchant Alliance |
E914147
|
entity |
| Predicate | allowsPlayersToRaiseEmissaryFlag |
P193578
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Merchant Alliance, allowsPlayersToRaiseEmissaryFlag, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowsPlayersToRaiseEmissaryFlag Context triple: [Merchant Alliance, allowsPlayersToRaiseEmissaryFlag, yes]
-
A.
coRaiserOfFlagWith
Indicates that one entity participated together with another entity in the act of raising a flag.
-
B.
usedRuseOfFlag
Indicates that one party employed the deceptive display or misuse of a flag (such as a national or identifying flag) to mislead or trick another party in the course of an action or interaction.
-
C.
raisedFlagDuring
Indicates that an entity raised or triggered a flag at some point during a specified event, process, or time interval.
-
D.
hasFlagstaff
Indicates that one entity possesses, contains, or is equipped with a flagstaff (a pole or staff for displaying a flag).
-
E.
isOnFlagOf
Indicates that something (typically a symbol, image, or design element) appears on or is depicted on a flag.
- F. None of above. chosen
Provenance (4 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_69fd49f6dbac81909744373a357b7982 |
completed | May 8, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69fd48ed68f481908374183c66a6b055 |
completed | May 8, 2026, 2:22 a.m. |
| PDg | Predicate description generation | batch_69fd49f612a4819096fe7d5a3bb439ba |
completed | May 8, 2026, 2:27 a.m. |
Created at: May 3, 2026, 4:13 p.m.