Triple
T27223716
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baure people |
E681350
|
entity |
| Predicate | colonialPeriodActivity |
P151034
|
FINISHED |
| Object | lived in Jesuit missions |
—
|
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: lived in Jesuit missions | Statement: [Baure people, colonialPeriodActivity, lived in Jesuit missions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: colonialPeriodActivity Context triple: [Baure people, colonialPeriodActivity, lived in Jesuit missions]
-
A.
colonialEraActivity
chosen
Indicates activities, practices, or events that took place during a colonial historical period.
-
B.
functionDuringColonialEra
Indicates that the function, role, or activity occurred or was in effect during the colonial era.
-
C.
colonialEraExperience
Indicates an entity’s experiences, conditions, or interactions that occurred during a period of colonial rule.
-
D.
usedInColonialPeriod
Indicates that something was utilized or in active use during a historical colonial period.
-
E.
colonialHistoryIncludes
Indicates that one entity’s colonial history encompasses, involves, or includes the other entity as part of its colonial past.
- 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_69eefac9f64c8190a07490fe0c8b72a3 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f64dbbaefc8190952b8320bf4397d8 |
completed | May 2, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f64cacd2c08190aed8a1761d0da679 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 27, 2026, 9:43 a.m.