Triple
T28585821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gurnet Point |
E723500
|
entity |
| Predicate | protectsEntranceTo |
P46861
|
FINISHED |
| Object | Plymouth Bay |
—
|
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: Plymouth Bay | Statement: [Gurnet Point, protectsEntranceTo, Plymouth Bay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: protectsEntranceTo Context triple: [Gurnet Point, protectsEntranceTo, Plymouth Bay]
-
A.
guardedEntranceTo
chosen
Indicates that one entity serves as a protective or controlling barrier for access to another entity’s entrance.
-
B.
hasEntranceControl
Indicates that an entity implements or is subject to mechanisms that regulate or control access to its entrance.
-
C.
hasEntrance
Indicates that one entity possesses or provides an entry point or access way to another entity or space.
-
D.
hasEntranceOn
Indicates that one entity’s entrance or access point is located on or faces a specified side, boundary, or feature of another entity.
-
E.
protectsApproachTo
Indicates that one entity safeguards or defends the way or route by which another entity is accessed or approached.
- 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_69f01d7f92e481909847f5f3f3174a89 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f66d7765208190b87b1cc6d96a151c |
completed | May 2, 2026, 9:32 p.m. |
| PD | Predicate disambiguation | batch_69f66abfdaf08190a55f14c70be6fd4d |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 28, 2026, 4:17 a.m.