Triple
T965576
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rollo |
E20829
|
entity |
| Predicate | receivedTerritory |
P22232
|
FINISHED |
| Object | lands around Rouen |
—
|
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: lands around Rouen | Statement: [Rollo, receivedTerritory, lands around Rouen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: receivedTerritory Context triple: [Rollo, receivedTerritory, lands around Rouen]
-
A.
returnedTerritoryName
Indicates the name of a territory that has been given back or restored to a previous owner or controlling entity.
-
B.
claimsTerritory
Indicates that one entity asserts ownership, control, or sovereign rights over a specific geographic area or region.
-
C.
territoryIncluded
Indicates that one territory is geographically or administratively contained within another territory.
-
D.
territoryRepresentation
Indicates that one entity serves as a representation, model, or depiction of a specific territory or geographic area for another entity.
-
E.
territorialStatus
Indicates the legal or political condition of control, sovereignty, or jurisdiction that applies to a specific territory.
- F. None of above. chosen
Provenance (4 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_69a493b33d2c81909c52c369d3ca8436 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b431d61481908b53490e99670363 |
completed | March 1, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69a4b2a42c1481908d940cbe0aefdd3b |
completed | March 1, 2026, 9:41 p.m. |
| PDg | Predicate description generation | batch_69a4b36064a48190b85c402f32cbadd1 |
completed | March 1, 2026, 9:45 p.m. |
Created at: March 1, 2026, 7:40 p.m.