Triple
T8700955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cottenham |
E206528
|
entity |
| Predicate | fenEdgeLocation |
P31590
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Cottenham, fenEdgeLocation, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fenEdgeLocation Context triple: [Cottenham, fenEdgeLocation, yes]
-
A.
formsEdgeOf
chosen
Indicates that one entity constitutes a boundary or outer limit of another entity.
-
B.
eraLocation
Indicates the place or geographic context in which a particular historical era or time period occurs or is primarily associated.
-
C.
benchLocation
Indicates that a bench is located at or associated with a specific place or position.
-
D.
deltaLocation
Indicates a change or difference between two locations, typically specifying how one location has shifted relative to another.
-
E.
farDetectorLocation
Indicates that one entity is located at or corresponds to the position of a far (distant) detector relative to another reference point or system.
- 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_69ca83555b6c8190abe930dd397e863b |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc58b27bd48190a5f76111ee657553 |
completed | March 31, 2026, 11:28 p.m. |
| PD | Predicate disambiguation | batch_69cc456bda508190a9aa0fb92760739e |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:34 p.m.