Triple
T30972597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ebro Treaty |
E789137
|
entity |
| Predicate | sphereOfInfluenceSouthOfBoundary |
P2828
|
FINISHED |
| Object | Carthage |
—
|
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: Carthage | Statement: [Ebro Treaty, sphereOfInfluenceSouthOfBoundary, Carthage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sphereOfInfluenceSouthOfBoundary Context triple: [Ebro Treaty, sphereOfInfluenceSouthOfBoundary, Carthage]
-
A.
sphereOfInfluence
chosen
Indicates the area or domain within which an entity exerts significant control, impact, or authority over others.
-
B.
boundaryTypeSouth
Indicates the type or nature of the boundary that lies to the south of a given entity.
-
C.
hasSouthBorder
Indicates that one entity shares its southern boundary or border with another entity.
-
D.
southernBoundaryReference
Indicates that one entity is used as the reference or defining limit for the southern boundary of another entity.
-
E.
hasHistoricalRegionOnSouthernBoundary
Indicates that an entity’s southern boundary is adjacent to or defined by a specific historical region.
- 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_69f224c4831c8190be53924ec25a150a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f697eabb048190bc01a830f14942c6 |
completed | May 3, 2026, 12:33 a.m. |
| PD | Predicate disambiguation | batch_69f69664142c8190bc695501056b0236 |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 8:55 p.m.