Triple
T30880489
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roger Mason |
E786595
|
entity |
| Predicate | notableDiscoveryLocation |
P91990
|
FINISHED |
| Object | Charnwood Forest, Leicestershire |
E219032
|
NE 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: Charnwood Forest, Leicestershire | Statement: [Roger Mason, notableDiscoveryLocation, Charnwood Forest, Leicestershire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableDiscoveryLocation Context triple: [Roger Mason, notableDiscoveryLocation, Charnwood Forest, Leicestershire]
-
A.
notableLocation
Indicates that a location is especially significant, prominent, or noteworthy in relation to the subject.
-
B.
notableDiscoveryAtSite
chosen
Indicates that an entity is recognized for having made an important discovery at a particular site.
-
C.
notableLocationOn
Indicates that a particular location is especially significant or noteworthy in relation to a specified entity or context.
-
D.
notablePlace
Indicates that a place is especially significant, famous, or noteworthy in relation to the subject.
-
E.
notableLocationDocumented
Indicates that a specific location associated with an entity is recorded or documented as notable in some source or reference.
- F. None of above.
Provenance (4 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_69f224bae17c8190bb3a6a28e3d019df |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a292af72f508190b11b5d4d193983c4 |
completed | June 10, 2026, 9:14 a.m. |
| PD | Predicate disambiguation | batch_6a0379e2fac0819089b522db3260028c |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 8:48 p.m.