Triple
T16785088
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rhodian–Quill conflict |
E407950
|
entity |
| Predicate | hasOutcomeForQuill |
P33358
|
FINISHED |
| Object | enslavement by Rhodians |
—
|
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: enslavement by Rhodians | Statement: [Rhodian–Quill conflict, hasOutcomeForQuill, enslavement by Rhodians]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOutcomeForQuill Context triple: [Rhodian–Quill conflict, hasOutcomeForQuill, enslavement by Rhodians]
-
A.
hasOutcomeIndicator
Indicates that something is associated with a specific measure or indicator used to evaluate its outcome or results.
-
B.
hasEventOutcome
chosen
Indicates that a particular event results in, leads to, or is associated with a specific outcome.
-
C.
hasProposedOutcome
Indicates that an action, decision, or process is associated with a suggested or anticipated result that is being put forward but not yet realized or confirmed.
-
D.
hasConclusion
Indicates that something leads to, results in, or is associated with a particular conclusion.
-
E.
hasOutputStatus
Indicates that an entity is associated with a particular state or condition of its produced output.
- 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_69d8839270588190886720d9519bbf8f |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3b21996cc81909deb88545af7079f |
completed | April 18, 2026, 4:32 p.m. |
| PD | Predicate disambiguation | batch_69e319cf691c819083e39225f5777ef0 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:22 a.m.