Triple
T38643684
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Warfronts |
E938664
|
entity |
| Predicate | factionParticipation |
P4470
|
FINISHED |
| Object | Alliance |
—
|
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: Alliance | Statement: [Warfronts, factionParticipation, Alliance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: factionParticipation Context triple: [Warfronts, factionParticipation, Alliance]
-
A.
participation
chosen
Indicates that an entity takes part in, contributes to, or is involved in a shared activity, event, or process with others.
-
B.
establishesParticipationIn
Indicates that one entity formally creates or defines another entity’s involvement in an activity, event, or group.
-
C.
announcedParticipationIn
Indicates that an entity has publicly declared its intention to take part in a specific event, activity, or initiative.
-
D.
endedParticipationOf
Indicates that one entity caused or marked the termination of another entity’s involvement in an activity, event, or relationship.
-
E.
organizedParticipationIn
Indicates that one entity arranged, coordinated, or led another entity’s involvement in an event, activity, or process.
- 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_69f76ed948ec81908ce7811608a8f359 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd6dbd1b648190b1a0b391c03aebc5 |
completed | May 8, 2026, 4:59 a.m. |
| PD | Predicate disambiguation | batch_69fd6a9020548190bbfa845360ac85fb |
completed | May 8, 2026, 4:46 a.m. |
Created at: May 3, 2026, 4:32 p.m.