Triple
T24006594
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monumento a Padre Anchieta em Cananéia |
E594404
|
entity |
| Predicate | subjectActivityRegion |
P63149
|
FINISHED |
| Object | colonial Brazil |
—
|
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: colonial Brazil | Statement: [Monumento a Padre Anchieta em Cananéia, subjectActivityRegion, colonial Brazil]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subjectActivityRegion Context triple: [Monumento a Padre Anchieta em Cananéia, subjectActivityRegion, colonial Brazil]
-
A.
area of activity
Indicates the domain, field, or sphere in which an entity is active or carries out its primary functions or operations.
-
B.
politicalActivityRegion
Indicates the geographic region or area in which a political activity takes place or is focused.
-
C.
hasActivityRegion
chosen
Indicates the geographic or spatial region within which an activity occurs or is applicable.
-
D.
регионДеятельности
Indicates the geographic region or area in which an entity carries out its activities or operations.
-
E.
continentOfActivity
Indicates the continent on which an entity primarily operates, is active, or conducts its main activities.
- 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_69e288b9ecf08190b8c94a278f5674fe |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d46a6ba48190b0cce0b134dfb35f |
completed | April 29, 2026, 9:50 a.m. |
| PD | Predicate disambiguation | batch_69f17639d23c8190bed93434e2f9230a |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 9:40 p.m.