Triple
T27677743
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southern Britain |
E697826
|
entity |
| Predicate | oftenIncludesRegion |
P97931
|
FINISHED |
| Object | Wales |
—
|
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: Wales | Statement: [Southern Britain, oftenIncludesRegion, Wales]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenIncludesRegion Context triple: [Southern Britain, oftenIncludesRegion, Wales]
-
A.
sometimesIncludesTerritory
Indicates that one entity occasionally, but not consistently, encompasses or contains the territory of another entity.
-
B.
includedRegions
chosen
Indicates that certain regions are contained within, or form part of, a larger specified region or set of regions.
-
C.
distributionRegionsInclude
Indicates that certain geographic or market regions are encompassed within the overall distribution coverage of a product or service.
-
D.
endsInRegion
Indicates that an entity’s spatial or temporal extent terminates within the boundaries of a specified region.
-
E.
hasRegion
Indicates that an entity includes, contains, or is associated with a specific geographic or administrative region as part of its scope or structure.
- 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_69ef590d458c81909583290c3cd0478b |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f6df450014819099d118e5c2d697fa |
completed | May 3, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69f6de07836481908785cde9c511920b |
completed | May 3, 2026, 5:32 a.m. |
Created at: April 27, 2026, 2:44 p.m.