Triple
T28661015
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Brundisium |
E725466
|
entity |
| Predicate | assignedTerritoryTo |
P88410
|
FINISHED |
| Object | Octavian |
—
|
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: Octavian | Statement: [Treaty of Brundisium, assignedTerritoryTo, Octavian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: assignedTerritoryTo Context triple: [Treaty of Brundisium, assignedTerritoryTo, Octavian]
-
A.
assignedToTerritoryType
Indicates that an entity has been allocated or linked to a specific type of territory within a defined territorial classification system.
-
B.
assignedToArea
chosen
Indicates that something has been allocated or designated to a specific area or region.
-
C.
assignedTo
Indicates that responsibility for a task, item, or role has been designated to a specific entity.
-
D.
assignedUnder
Indicates that one entity has been given responsibility, duty, or authority to act within the scope, supervision, or framework defined by another entity.
-
E.
assignedAs
Indicates that one entity is designated or appointed to perform a specific role, task, or function in relation to 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_69f01d84f5f0819087ab5e6143b14ed7 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f658ee40088190b71e1219407690d0 |
completed | May 2, 2026, 8:05 p.m. |
| PD | Predicate disambiguation | batch_69f65760fd3081908ffe014a5e2bf069 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 4:58 a.m.