Triple
T3609039
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beira Litoral |
E76438
|
entity |
| Predicate | dissolvedInAdministrativeReform |
P133
|
FINISHED |
| Object | 1976 |
—
|
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: 1976 | Statement: [Beira Litoral, dissolvedInAdministrativeReform, 1976]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dissolvedInAdministrativeReform Context triple: [Beira Litoral, dissolvedInAdministrativeReform, 1976]
-
A.
municipalityReform
Indicates a formal reorganization or restructuring of a municipality’s administrative boundaries, governance, or status.
-
B.
dissolvedOrAbolished
chosen
Indicates that an organization, institution, or formal entity has been officially terminated, disbanded, or ceased to exist.
-
C.
restructuredGovernmentOf
Indicates that one entity has reorganized or significantly altered the governmental structure or system of another entity.
-
D.
lastReform
Indicates the most recent reform or change that was applied to an entity, typically linking the entity to its latest reform event or version.
-
E.
isPartOfReform
Indicates that an action, measure, or component belongs to, contributes to, or is included within a broader reform initiative or process.
- 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_69ad85da0ba481908b3b48c69efe2b98 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc22a3cf081908c20b6fb55be0db2 |
completed | March 8, 2026, 6:38 p.m. |
| PD | Predicate disambiguation | batch_69adb83d8b1c8190b3bddbc5dc995a87 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:22 p.m.