Triple
T29021213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Italy and Africa |
E737455
|
entity |
| Predicate | encompassedTerritory |
P11790
|
FINISHED |
| Object | Italian peninsula |
—
|
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: Italian peninsula | Statement: [Italy and Africa, encompassedTerritory, Italian peninsula]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: encompassedTerritory Context triple: [Italy and Africa, encompassedTerritory, Italian peninsula]
-
A.
territorialExtent
Indicates the geographic area or spatial range over which something extends, applies, or has jurisdiction.
-
B.
mainTerritoryOfInfluence
Indicates the primary geographic area where an entity exerts the most significant control, impact, or influence.
-
C.
territoryIncluded
chosen
Indicates that one territory is geographically or administratively contained within another territory.
-
D.
territoryCorrespondedTo
Indicates that one territory matched, aligned with, or was equivalent to another territory in scope, boundaries, or designation.
-
E.
territoryOriginallyIncluded
Indicates that an earlier or original territorial boundary encompassed the referenced area or 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_69f077ee19f881909af48f9cab00a2e5 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f66005ea00819085501231fe82cc5e |
completed | May 2, 2026, 8:35 p.m. |
| PD | Predicate disambiguation | batch_69f659d297cc8190b2b962ba30a1edb3 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 9:49 a.m.