Triple
T22523212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Portuguese Padroado |
E556830
|
entity |
| Predicate | finalDismantling |
P77993
|
FINISHED |
| Object | 20th 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: 20th century | Statement: [Portuguese Padroado, finalDismantling, 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalDismantling Context triple: [Portuguese Padroado, finalDismantling, 20th century]
-
A.
dismantledBy
Indicates that something has been taken apart, disassembled, or broken down by a particular agent or entity.
-
B.
dismantledIn
chosen
Indicates that an entity was taken apart, disassembled, or broken down within a specified context, such as a particular time, place, or event.
-
C.
aimedToBeDismantledBy
Indicates that one entity was the intended target of dismantling or disassembly by another entity.
-
D.
partlyDismantledBy
Indicates that an entity has been only partially taken apart, removed, or deconstructed by another agent or process.
-
E.
dismembered
Indicates that one entity has cut or torn another entity’s body into separate parts, typically removing limbs or sections.
- 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_69e11e5657e881909f16ca58352c50da |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15e338dfc819082e1eeede3805fb9 |
completed | April 29, 2026, 1:26 a.m. |
| PD | Predicate disambiguation | batch_69ee625e3b408190a60c759fb0b28fe2 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 16, 2026, 8:50 p.m.