Triple
T31603899
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LND |
E806422
|
entity |
| Predicate | locationOfIdentifiedEntity |
P47308
|
FINISHED |
| Object | Regent’s Park, London |
E44922
|
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: Regent’s Park, London | Statement: [LND, locationOfIdentifiedEntity, Regent’s Park, London]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationOfIdentifiedEntity Context triple: [LND, locationOfIdentifiedEntity, Regent’s Park, London]
-
A.
subjectLocation
chosen
Indicates that one entity is located at, in, or near the place or position specified by another entity.
-
B.
objectLocation
Indicates that one entity is located at, in, or on another entity or spatial region.
-
C.
locationOfSee
Indicates a relationship where a particular place is the setting or site in which an act of seeing or visual perception occurs.
-
D.
locatedWith
Indicates that two or more entities are situated together in the same place or spatial context.
-
E.
locationOfFacts
Indicates that certain facts or pieces of information are situated, stored, or found at a particular location or source.
- 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_69f348d54ccc8190a03b5df9a2b40b25 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a01b130f6808190b86442fb16930e6e |
completed | May 11, 2026, 10:36 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2e7fc0f73c81908f11993a8497311e |
completed | June 14, 2026, 10:17 a.m. |
| PD | Predicate disambiguation | batch_6a01b023157881909a802e06eced3e2f |
completed | May 11, 2026, 10:32 a.m. |
Created at: April 30, 2026, 10:34 p.m.