Triple
T24946251
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Waa |
E624190
|
entity |
| Predicate | hasOppositionOrComplement |
P43226
|
FINISHED |
| Object | Bunjil |
—
|
NE NERFINISHED |
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: Bunjil | Statement: [Waa, hasOppositionOrComplement, Bunjil]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOppositionOrComplement Context triple: [Waa, hasOppositionOrComplement, Bunjil]
-
A.
hasOppositionType
Indicates that an entity is associated with a specific kind or category of opposition it faces or represents.
-
B.
hasOppositionalElements
Indicates that something contains components or aspects that are in conflict, contrast, or opposition to each other.
-
C.
isOppositionCounterpartOf
chosen
Indicates a relationship where one entity serves as the opposing or counterpart force, side, or position to another within a conflict, competition, or contrast.
-
D.
hasOppositionFunction
Indicates that one entity serves to counteract, resist, or work against the function or effect of another entity.
-
E.
hasOpposedCondition
Indicates that one condition stands in direct opposition or contradiction to another condition.
- 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_69e2ff22e4c48190a0444b5a044f14e8 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f5f6baf2d48190a6a4cd6501be87d2 |
completed | May 2, 2026, 1:06 p.m. |
| PD | Predicate disambiguation | batch_69f5afd5baac8190bb8ed576813c8591 |
completed | May 2, 2026, 8:03 a.m. |
Created at: April 18, 2026, 5:54 a.m.