Triple
T38406058
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | One-Eyed Willy |
E901330
|
entity |
| Predicate | bodyRemainsLocatedOn |
P76038
|
FINISHED |
| Object | the ship Inferno |
—
|
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: the ship Inferno | Statement: [One-Eyed Willy, bodyRemainsLocatedOn, the ship Inferno]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bodyRemainsLocatedOn Context triple: [One-Eyed Willy, bodyRemainsLocatedOn, the ship Inferno]
-
A.
locatedOnBody
Indicates that one entity is physically situated on the surface or external part of another entity’s body.
-
B.
bodyFound
Indicates that the location or circumstance where a body was discovered has been identified or recorded.
-
C.
sourceLocatedOn
Indicates that the source entity is physically situated on the surface or area of the target entity.
-
D.
objectLocation
chosen
Indicates that one entity is located at, in, or on another entity or spatial region.
-
E.
seatOnBody
Indicates that one entity functions as a seat or seating surface that is physically attached or integrated to a body or body-like structure.
- 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_69f76e61e79c81908b787d83b46ab92b |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fcd1499e2c81909bafd84dc4810f45 |
completed | May 7, 2026, 5:52 p.m. |
| PD | Predicate disambiguation | batch_69fcccf024ec819086383ffbb6cfc036 |
completed | May 7, 2026, 5:33 p.m. |
Created at: May 3, 2026, 4:31 p.m.