Triple
T446194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Overseas Territories |
E7025
|
entity |
| Predicate | numberOfConstituentTerritories |
P3811
|
FINISHED |
| Object | 14 |
—
|
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: 14 | Statement: [British Overseas Territories, numberOfConstituentTerritories, 14]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfConstituentTerritories Context triple: [British Overseas Territories, numberOfConstituentTerritories, 14]
-
A.
numberOfUnionTerritories
Indicates the total count of union territories associated with a given country or administrative entity.
-
B.
hasNumberOfDependentTerritories
chosen
Indicates the quantitative relationship specifying how many dependent territories are associated with a given entity.
-
C.
hasOverseasTerritory
Indicates that one entity possesses or controls a territory located outside its own primary geographic or sovereign domain.
-
D.
associatedConfederationCount
Indicates the number of distinct confederations with which an entity is associated.
-
E.
numberOfProvinces
Indicates the total count of provinces associated with a given entity or within a specified region or country.
- 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_69a2e7e4676c81909ea0dbdecac0687c |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ef62c7a88190851fcd57658b4102 |
completed | Feb. 28, 2026, 1:36 p.m. |
| PD | Predicate disambiguation | batch_69a2eddfb5508190a4e06e1b260d8b2b |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.