Triple
T37131446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Jersey |
E919527
|
entity |
| Predicate | anchoredAt |
P187177
|
FINISHED |
| Object | Wallabout 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: Wallabout Bay | Statement: [HMS Jersey, anchoredAt, Wallabout Bay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: anchoredAt Context triple: [HMS Jersey, anchoredAt, Wallabout Bay]
-
A.
anchoredBy
Indicates that one entity is fixed, secured, or held in place by another acting as its anchor.
-
B.
anchorPoint
Indicates a fixed reference position used to attach, align, or position one entity relative to another.
-
C.
attachedTo
Indicates that one entity is physically or logically fastened, connected, or joined to another entity.
-
D.
coAnchorWith
Indicates that two or more people jointly serve as anchors or hosts of the same program, segment, or broadcast.
-
E.
posedAt
Indicates that something (such as a question, challenge, or problem) is directed toward or presented to a particular target or context.
- 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_69f76e9d13e48190a108f7fbf80ff375 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb344c60f8819090f2e21e1e61d621 |
completed | May 6, 2026, 12:30 p.m. |
| PD | Predicate disambiguation | batch_69fb2f642db08190b562725502c74ea6 |
completed | May 6, 2026, 12:09 p.m. |
| PDg | Predicate description generation | batch_69fb344ba5408190a6fe8face293d88b |
completed | May 6, 2026, 12:30 p.m. |
Created at: May 3, 2026, 4:15 p.m.