Triple
T26103929
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Nore anchorage |
E658486
|
entity |
| Predicate | guardedApproachTo |
P159945
|
FINISHED |
| Object | London |
—
|
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: London | Statement: [The Nore anchorage, guardedApproachTo, London]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: guardedApproachTo Context triple: [The Nore anchorage, guardedApproachTo, London]
-
A.
controlledApproachTo
Indicates a deliberate, regulated, or carefully managed way of proceeding toward or dealing with another entity.
-
B.
protectedApproach
Indicates that one entity safeguards, supports, or enables another entity’s method, path, or manner of proceeding so it can be carried out safely or without interference.
-
C.
usedToApproach
Indicates that one entity employed another entity as a means or method to move closer to or reach a target entity or location.
-
D.
controlledApproachesTo
Indicates that one entity regulates or manages the methods or ways in which another entity can be approached.
-
E.
approachOver
Indicates that one entity moves closer to another entity from a position above or higher than it.
- F. None of above. chosen
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_69ee5bc09c288190bc42a11972841383 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f60774d1648190a2616433371e1d51 |
completed | May 2, 2026, 2:17 p.m. |
| PD | Predicate disambiguation | batch_69f5b0021da88190bdd4cf2698c23edf |
completed | May 2, 2026, 8:04 a.m. |
| PDg | Predicate description generation | batch_69f5f6b32a8881909baa0db57b80d56a |
completed | May 2, 2026, 1:05 p.m. |
Created at: April 26, 2026, 7:57 p.m.