Triple
T22123513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Welser family |
E546732
|
entity |
| Predicate | lostConcession |
P20740
|
FINISHED |
| Object | Venezuela colony in 16th century |
—
|
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: Venezuela colony in 16th century | Statement: [Welser family, lostConcession, Venezuela colony in 16th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lostConcession Context triple: [Welser family, lostConcession, Venezuela colony in 16th century]
-
A.
lostSovereignty
Indicates that an entity has ceased to possess independent authority or control over its own governance or territory.
-
B.
lost
chosen
Indicates that an entity no longer possesses or has been deprived of another entity it previously had.
-
C.
lostTerritoryBy
Indicates that one entity has had control or ownership of a territory taken away by another entity.
-
D.
loserStatus
Indicates that an entity has been judged or designated as the loser in a particular comparison, contest, or evaluative context.
-
E.
lostDuring
Indicates that something ceased to be in possession or was no longer retained while a particular event, process, or time period was occurring.
- 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_69e11e39bf348190b541bfa16a7b71e0 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f1298016e081909d00015ca516d9fd |
completed | April 28, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69e71b2ed7348190b6fa2e52f54393fb |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:31 p.m.