Triple
T25191521
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Newburn |
E630883
|
entity |
| Predicate | ScottishPosition |
P158014
|
FINISHED |
| Object | north bank of the River Tyne |
—
|
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: north bank of the River Tyne | Statement: [Battle of Newburn, ScottishPosition, north bank of the River Tyne]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ScottishPosition Context triple: [Battle of Newburn, ScottishPosition, north bank of the River Tyne]
-
A.
scottishTeam
Indicates that the team is associated with or originates from Scotland.
-
B.
monarchOfScottishSide
Indicates that the subject is the reigning monarch associated with the Scottish side or faction in a given context.
-
C.
hasCapitalCityOfScotland
Indicates the relationship in which an entity has, as its capital city, the city that serves as the capital of Scotland.
-
D.
ScottishCommander
Indicates that an entity serves as a military commander who is Scottish or associated with Scotland.
-
E.
ScotlandGroupPositionAfterMatch
Indicates the position or ranking of the Scotland group in the standings immediately after a specific match has been completed.
- 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_69e75a8a6d088190ba1e82a4345225e7 |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f46e0f69b081908b72abcd18ab9c67 |
completed | May 1, 2026, 9:10 a.m. |
| PD | Predicate disambiguation | batch_69f44d8043b081908bbffd7f044b4f26 |
completed | May 1, 2026, 6:51 a.m. |
| PDg | Predicate description generation | batch_69f45300bd488190bb1d4160f5534ef6 |
completed | May 1, 2026, 7:15 a.m. |
Created at: April 21, 2026, 12:45 p.m.