Triple
T1236200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inter caetera |
E26552
|
entity |
| Predicate | limitedPortugalTo |
P24812
|
FINISHED |
| Object | lands east of the demarcation line |
—
|
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 east of the demarcation line | Statement: [Inter caetera, limitedPortugalTo, lands east of the demarcation line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: limitedPortugalTo Context triple: [Inter caetera, limitedPortugalTo, lands east of the demarcation line]
-
A.
porte
Indicates that an entity carries, wears, or bears another entity (such as an object, attribute, or characteristic).
-
B.
hasCitizenshipRestriction
Indicates that there is a legal or policy-based limitation on who can obtain or hold citizenship in a given context.
-
C.
nameInPortuguese
Indicates that an entity is referred to by a specific name when expressed in the Portuguese language.
-
D.
usedToRestrictEmigrationTo
Indicates that an entity implemented measures or policies to limit or control people leaving a particular place or jurisdiction.
-
E.
passesThroughCountry
Indicates that a route, path, or object traverses or crosses within the boundaries of a specified country.
- 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_69a4948571c88190a9191e451e6035fd |
completed | March 1, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69a4bf17e0bc8190a066561e6b629fc0 |
completed | March 1, 2026, 10:35 p.m. |
| PD | Predicate disambiguation | batch_69a4bb67d52c8190815d6356b79d6ed5 |
completed | March 1, 2026, 10:19 p.m. |
| PDg | Predicate description generation | batch_69a4bbf83584819088c69366f58586cc |
completed | March 1, 2026, 10:21 p.m. |
Created at: March 1, 2026, 7:47 p.m.