Triple
T26029266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UNIA-ACL |
E647382
|
entity |
| Predicate | hadDivisionIn |
P75887
|
FINISHED |
| Object | Central America |
—
|
NE NERFINISHED |
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: Central America | Statement: [UNIA-ACL, hadDivisionIn, Central America]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadDivisionIn Context triple: [UNIA-ACL, hadDivisionIn, Central America]
-
A.
hadDivisionInCountry
chosen
Indicates that an organization or entity maintained a formal division, branch, or subsidiary operating within a specified country.
-
B.
hadInternalDivision
Indicates that an entity experienced a split or conflict within its own members, factions, or components.
-
C.
hasCivilDivision
Indicates that one administrative or political entity is subdivided into, or is associated with, a specific civil division (such as a county, district, or municipality).
-
D.
dividedIn
Indicates that one entity is partitioned or separated into multiple distinct parts, sections, or groups represented by another entity.
-
E.
containsDivision
Indicates that one entity includes or encompasses a subdivision or internal division of another entity.
- 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_69e77e8b60e88190a3b26c4f0032a2c2 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f605ee5ba88190bc99652ac24b69b0 |
completed | May 2, 2026, 2:10 p.m. |
| PD | Predicate disambiguation | batch_69f602d07590819085ac34b189613104 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 22, 2026, 9:05 a.m.