Triple
T37898233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baron Apsley |
E945337
|
entity |
| Predicate | hasConnectionWithPark |
P62478
|
FINISHED |
| Object | Hyde Park, London |
E71303
|
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: Hyde Park, London | Statement: [Baron Apsley, hasConnectionWithPark, Hyde Park, London]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasConnectionWithPark Context triple: [Baron Apsley, hasConnectionWithPark, Hyde Park, London]
-
A.
associatedWithPark
chosen
Indicates a relationship in which an entity is connected or linked in some relevant way to a particular park.
-
B.
hasParkAccess
Indicates that an entity is permitted to enter, use, or otherwise access a specified park or park area.
-
C.
hasParkingConnection
Indicates that one entity is linked to another through a parking-related connection, such as shared access, adjacency, or functional association with parking facilities.
-
D.
hasParkStatus
Indicates that an entity holds a particular designation or status related to being a park (e.g., national park, city park, protected parkland).
-
E.
hasParkSection
Indicates that one entity includes, contains, or is associated with a specific section or area of a park.
- 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_69f76ef0e8708190987c7254ed8c7abe |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a415d1c9f748190a87010559e1c7ad4 |
completed | June 28, 2026, 5:42 p.m. |
| PD | Predicate disambiguation | batch_6a037a192a008190a9917688a9e804f4 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:19 p.m.