Triple
T37130478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wings of Time |
E919501
|
entity |
| Predicate | setAgainst |
P176662
|
FINISHED |
| Object | open sea |
—
|
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: open sea | Statement: [Wings of Time, setAgainst, open sea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setAgainst Context triple: [Wings of Time, setAgainst, open sea]
-
A.
isSetAgainst
chosen
Indicates a situation in which one entity is positioned in opposition or contrast to another, often implying conflict, resistance, or competing interests.
-
B.
setAgainstEvent
Indicates that one event is positioned or framed in opposition or contrast to another event.
-
C.
turnAgainst
Indicates a shift in allegiance where one entity begins to oppose, betray, or act hostile toward another it previously supported or was aligned with.
-
D.
opposedBy
Indicates that one entity actively resists, disagrees with, or works against the actions, views, or position of another entity.
-
E.
usedAgainst
Indicates that one entity is employed, applied, or deployed in opposition to, or for the purpose of affecting, another entity.
- 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_69f76e9d13e48190a108f7fbf80ff375 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb344c60f8819090f2e21e1e61d621 |
completed | May 6, 2026, 12:30 p.m. |
| PD | Predicate disambiguation | batch_69fb2f642db08190b562725502c74ea6 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:15 p.m.