Triple
T30460177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tin Can Island |
E774982
|
entity |
| Predicate | mailCollectedFrom |
P169463
|
FINISHED |
| Object | passing ships offshore |
—
|
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: passing ships offshore | Statement: [Tin Can Island, mailCollectedFrom, passing ships offshore]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mailCollectedFrom Context triple: [Tin Can Island, mailCollectedFrom, passing ships offshore]
-
A.
mailedTo
Indicates that something was sent or delivered by mail from one entity to another as the recipient.
-
B.
mailRoute
Indicates a route or path along which mail or postal items are transported between locations.
-
C.
mailboxModel
Indicates a relationship where an entity functions as or is associated with a specific mailbox configuration or structural model.
-
D.
addressedFor
Indicates that something is directed, designated, or intended for a particular recipient or target.
-
E.
receivedFor
Indicates that something was obtained, accepted, or taken into possession on behalf of or for the benefit of a specified 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_69f22494fb60819095d893de0284f886 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f686f01dc88190a6ca46fc5c80a486 |
completed | May 2, 2026, 11:21 p.m. |
| PD | Predicate disambiguation | batch_69f678d2196c8190b9d0d2fcd47cc539 |
completed | May 2, 2026, 10:21 p.m. |
| PDg | Predicate description generation | batch_69f67d31cc60819084f64bd056e1ea4d |
completed | May 2, 2026, 10:39 p.m. |
Created at: April 29, 2026, 8:10 p.m.