Triple
T27554285
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Battles of the Fords of Isen |
E695591
|
entity |
| Predicate | setAtLocation |
P24794
|
FINISHED |
| Object | Fords of Isen |
—
|
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: Fords of Isen | Statement: [The Battles of the Fords of Isen, setAtLocation, Fords of Isen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setAtLocation Context triple: [The Battles of the Fords of Isen, setAtLocation, Fords of Isen]
-
A.
setLocation
chosen
Indicates assigning or updating the place or position where an entity is located.
-
B.
setRecordAt
Indicates assigning or updating a record at a specific position or location within a collection or data structure.
-
C.
posedAtLocation
Indicates that an entity is positioned or arranged in a deliberate pose at a specific location.
-
D.
definesLocation
Indicates that one entity specifies or establishes the spatial or geographic position of another entity.
-
E.
setWorldRecordLocation
Indicates the place where a world record was set or achieved.
- 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_69ef5387e97c8190a9dab040d21cd048 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f62f8e4ab88190bfe86343b948a401 |
completed | May 2, 2026, 5:08 p.m. |
| PD | Predicate disambiguation | batch_69f62c1921008190a62675a31f66a875 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 1:36 p.m.