Triple
T26211500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS President |
E655501
|
entity |
| Predicate | captureLocation |
P160048
|
FINISHED |
| Object | off Long Island, New York |
—
|
LITERAL 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: off Long Island, New York | Statement: [USS President, captureLocation, off Long Island, New York]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: captureLocation Context triple: [USS President, captureLocation, off Long Island, New York]
-
A.
coordinateLocation
Indicates that an entity is located at, or associated with, a specific geographic coordinate or set of coordinates.
-
B.
typeOfLocationCaptured
Indicates that a specific kind or category of location is what has been captured or recorded in a given context.
-
C.
agingLocation
Indicates the place where an entity undergoes an aging process or is stored to age over time.
-
D.
mapLocation
Indicates a relationship where an entity is associated with a specific position or area on a map.
-
E.
showLocation
Indicates that one entity displays or reveals the position or place of another entity.
- 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_69ee5b49adb4819086545280d4ef6337 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f60d1706d481908ca3c7c39ba0d157 |
completed | May 2, 2026, 2:41 p.m. |
| PD | Predicate disambiguation | batch_69f5b007ec1c819092e2c3605933f60b |
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, 8:52 p.m.