Triple
T7314135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Battle of Sherramuir |
E168166
|
entity |
| Predicate | portraysOutcomeAs |
P22390
|
FINISHED |
| Object | confused |
—
|
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: confused | Statement: [The Battle of Sherramuir, portraysOutcomeAs, confused]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: portraysOutcomeAs Context triple: [The Battle of Sherramuir, portraysOutcomeAs, confused]
-
A.
describesOutcomeOf
chosen
Indicates that one entity specifies or characterizes the result, consequence, or outcome produced by another entity or process.
-
B.
outcomeOf
Indicates that one entity is the result, consequence, or product that arises from another entity, event, or process.
-
C.
portraysState
Indicates that one entity visually or symbolically represents or depicts the condition, status, or situation of another entity.
-
D.
portrayalReceived
Indicates that an entity has been depicted or represented by another entity, such as through an image, performance, or description.
-
E.
portrayedAsFrom
Indicates that one entity is depicted or represented as originating from, or belonging to, the place or source specified by 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_69c6888d8e3c81909db79714903baf31 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6ec03a7248190beb1dec612725e5b |
completed | March 27, 2026, 8:43 p.m. |
| PD | Predicate disambiguation | batch_69c6e7705f4881909793071dee50c557 |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 3:02 p.m.