Triple
T4027921
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Council of the Gods |
E83636
|
entity |
| Predicate | hasOpposingFaction |
P53524
|
FINISHED |
| Object | gods favoring the Portuguese |
—
|
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: gods favoring the Portuguese | Statement: [Council of the Gods, hasOpposingFaction, gods favoring the Portuguese]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOpposingFaction Context triple: [Council of the Gods, hasOpposingFaction, gods favoring the Portuguese]
-
A.
hasFaction
Indicates that an entity is affiliated with, belongs to, or is represented by a particular faction or group.
-
B.
opponentForceAllegiance
Indicates that one force, group, or individual is aligned with or belongs to an opposing or enemy side in a conflict or competition.
-
C.
hasMajorFaction
Indicates that an entity possesses or is associated with a primary or dominant faction within a given context.
-
D.
hasOpposingSide
Indicates that one entity possesses or is associated with another entity that lies on the opposite or facing side relative to a reference orientation or boundary.
-
E.
opposingAlliance
Indicates that two entities belong to rival or mutually opposed alliances or factions.
- 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_69aed92e29ac819080f7a98b594fec05 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefaeec44881909a6c008eeae204df |
completed | March 9, 2026, 4:53 p.m. |
| PD | Predicate disambiguation | batch_69aef8fc78ec819092d4dab88d85a141 |
completed | March 9, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69aefa815f2c8190818c9ffd9d1bf478 |
completed | March 9, 2026, 4:51 p.m. |
Created at: March 9, 2026, 3:36 p.m.