Triple
T23037561
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parishes of Bermuda |
E573643
|
entity |
| Predicate | areTopLevelInternalDivisions |
P52755
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Parishes of Bermuda, areTopLevelInternalDivisions, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: areTopLevelInternalDivisions Context triple: [Parishes of Bermuda, areTopLevelInternalDivisions, true]
-
A.
topLevelDivisions
chosen
Indicates that one administrative or organizational unit is a primary, highest-level subdivision within a larger entity or system.
-
B.
hasDivisionLevel
Indicates that one entity is associated with a specific hierarchical or organizational division level of another entity.
-
C.
isMainDivisionOf
Indicates that one division functions as the primary or central division within, or in relation to, another organizational structure.
-
D.
topLevelDivisionCount
Indicates the number of primary administrative or organizational divisions directly under a given entity.
-
E.
isPartOfDivision
Indicates that one entity belongs to, or is contained within, a specific division of a larger organizational or structural unit.
- 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_69e245b911188190bc3d96326c847969 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f185111f0881908991fcd6cdc7db9f |
completed | April 29, 2026, 4:12 a.m. |
| PD | Predicate disambiguation | batch_69ef3ba004a48190885aece88efd1f52 |
completed | April 27, 2026, 10:34 a.m. |
Created at: April 17, 2026, 3:53 p.m.