Triple
T37661425
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | End Ship |
E937725
|
entity |
| Predicate | foundNearStructure |
P8203
|
FINISHED |
| Object | End City |
—
|
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: End City | Statement: [End Ship, foundNearStructure, End City]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundNearStructure Context triple: [End Ship, foundNearStructure, End City]
-
A.
foundInStructure
Indicates that an entity is located within, contained by, or structurally part of another entity or structure.
-
B.
seeLocatedNear
Indicates that one entity visually perceives another entity that is situated nearby in physical space.
-
C.
foundAs
Indicates that one entity is discovered, identified, or observed in the role, form, or state represented by another entity.
-
D.
occursNear
chosen
Indicates that one event or entity takes place or exists in close spatial proximity to another.
-
E.
foundUnder
Indicates that one entity is located beneath or below another entity in a way that it can be discovered or retrieved from that position.
- 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff49016dcc8190a8a43868c728b4f1 |
completed | May 9, 2026, 2:47 p.m. |
| PD | Predicate disambiguation | batch_69ff4891924c8190b5be340e2520e012 |
completed | May 9, 2026, 2:45 p.m. |
Created at: May 3, 2026, 4:18 p.m.