Triple
T2871197
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rhône |
E63564
|
entity |
| Predicate | reducedTerritoryAfter |
P19675
|
FINISHED |
| Object | 2015 |
—
|
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: 2015 | Statement: [Rhône, reducedTerritoryAfter, 2015]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reducedTerritoryAfter Context triple: [Rhône, reducedTerritoryAfter, 2015]
-
A.
reducedTerritoryOf
chosen
Indicates that one entity has caused a decrease in the size or extent of another entity's territory or area of control.
-
B.
receivedTerritory
Indicates that one entity was granted or took possession of a territory from another entity.
-
C.
definedTerritoryOf
Indicates that one entity specifies or establishes the official territorial boundaries or jurisdiction of another entity.
-
D.
territoryType
Indicates the specific kind or classification of a territory associated with an entity (e.g., country, region, zone, or jurisdiction type).
-
E.
partitionedTerritory
Indicates that a larger territory has been divided into distinct parts or regions, typically with defined boundaries or administrative separation.
- 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_69ab4c42fb8c8190b36e161d47c03b81 |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdfe2dcb48190a194253e733d14af |
completed | March 7, 2026, 8:20 a.m. |
| PD | Predicate disambiguation | batch_69abdd142e4c8190b424cb0c5ff40d04 |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:02 p.m.