Triple
T24761943
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swansea copper industry |
E619469
|
entity |
| Predicate | centeredOnArea |
P93967
|
FINISHED |
| Object | White Rock |
—
|
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: White Rock | Statement: [Swansea copper industry, centeredOnArea, White Rock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centeredOnArea Context triple: [Swansea copper industry, centeredOnArea, White Rock]
-
A.
centeredOnField
Indicates that one entity is positioned or focused around the central area of a specified field or domain.
-
B.
hasRegionCenter
Indicates that a region is associated with a specific central point or location that serves as its geometric or administrative center.
-
C.
targetArea
Indicates the specific area or region that is the intended focus or destination of an action or effect.
-
D.
hasCenterIn
chosen
Indicates that something is located, based, or primarily focused within a specified central place or area.
-
E.
underliesArea
Indicates that one entity forms the foundational basis or underlying support for a particular area or domain of activity, knowledge, or influence.
- 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_69e2fabbea94819092ed41348909622f |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f48b9b687881908fd87a2f5fa0b1e7 |
completed | May 1, 2026, 11:16 a.m. |
| PD | Predicate disambiguation | batch_69f48060597c8190a4414e4e4fcb1fec |
completed | May 1, 2026, 10:28 a.m. |
Created at: April 18, 2026, 4:27 a.m.