Triple
T22406474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Catuvellauni |
E553891
|
entity |
| Predicate | mainSettlementNear |
P138521
|
FINISHED |
| Object | modern St Albans |
—
|
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: modern St Albans | Statement: [Catuvellauni, mainSettlementNear, modern St Albans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainSettlementNear Context triple: [Catuvellauni, mainSettlementNear, modern St Albans]
-
A.
mainSettlement
Indicates that one settlement serves as the primary or most important settlement associated with a given area, region, or administrative unit.
-
B.
nearbySettlementRegion
Indicates that a settlement is located close to or within the surrounding area of a specified region.
-
C.
nearbySettlements
chosen
Indicates that one settlement is located close to another settlement in geographic space.
-
D.
hasNearestLargerSettlement
Indicates that one settlement is associated with the geographically closest settlement that is larger in size or population.
-
E.
mainSettlementLocatedOn
Indicates that the primary settlement of an area is situated on or directly adjacent to a specified geographic feature or location.
- 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_69e11e4da7048190b4387d422a9a0de5 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f158b835e88190a388e19577df771e |
completed | April 29, 2026, 1:02 a.m. |
| PD | Predicate disambiguation | batch_69e8989495bc81909d2699fce5992e28 |
completed | April 22, 2026, 9:44 a.m. |
Created at: April 16, 2026, 8:46 p.m.