Triple
T28410322
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CL BR |
E719644
|
entity |
| Predicate | findspotRegion |
P9687
|
FINISHED |
| Object | southern Britain |
—
|
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: southern Britain | Statement: [CL BR, findspotRegion, southern Britain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: findspotRegion Context triple: [CL BR, findspotRegion, southern Britain]
-
A.
foundInRegion
chosen
Indicates that something is located within, occurs in, or is associated with a specific geographic or spatial region.
-
B.
museumRegion
Indicates that a museum is located within or associated with a particular geographic region.
-
C.
archaeologicalRegions
Indicates a relationship where specific areas are designated or recognized as regions of archaeological interest, activity, or significance.
-
D.
originalFindspot
Indicates the location where an object or artifact was first discovered or found in situ.
-
E.
heritageLocation
Indicates that a location is recognized or designated as having cultural, historical, or natural heritage significance in relation to something.
- 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_69eff6f0f37c8190b37bc6fab08a9449 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f64e37f7fc819083809149b6661e3c |
completed | May 2, 2026, 7:19 p.m. |
| PD | Predicate disambiguation | batch_69f64caede108190a35cc7cbfead866f |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 28, 2026, 1:26 a.m.