Triple
T3196001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of San Ildefonso (1800) |
E66935
|
entity |
| Predicate | typeOfTransfer |
P27343
|
FINISHED |
| Object | territorial retrocession |
—
|
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: territorial retrocession | Statement: [Treaty of San Ildefonso (1800), typeOfTransfer, territorial retrocession]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfTransfer Context triple: [Treaty of San Ildefonso (1800), typeOfTransfer, territorial retrocession]
-
A.
transferType
chosen
Indicates the specific method or category of how something is transferred from one entity to another.
-
B.
transmissionType
Indicates the method or medium through which something is transmitted or conveyed from one entity to another.
-
C.
hasTransfer
Indicates a relationship where something is moved or conveyed from one entity or location to another.
-
D.
transferMode
Indicates the method or mechanism by which something is transferred from one entity to another.
-
E.
typeOfSettlement
Indicates the specific category or classification of a settlement (e.g., city, town, village) that characterizes what kind of settlement it is.
- 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_69ad8588ba18819086a10951c32ecb80 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada7177b488190b7a1b40ff3fae15f |
completed | March 8, 2026, 4:43 p.m. |
| PD | Predicate disambiguation | batch_69ad9e05e4f48190adbe4366cdba2349 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:07 p.m.