Triple
T25764406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Blue Ghost |
E648838
|
entity |
| Predicate | associatedWithShipName |
P124609
|
FINISHED |
| Object | Lexington |
—
|
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: Lexington | Statement: [The Blue Ghost, associatedWithShipName, Lexington]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithShipName Context triple: [The Blue Ghost, associatedWithShipName, Lexington]
-
A.
shipNameWith
Indicates that a ship is associated with or identified by a particular name.
-
B.
shipAssociatedWith
Indicates that there is a relevant connection or involvement between a ship and another entity, such as ownership, operation, registration, or functional association.
-
C.
hasShipName
chosen
Indicates that an entity (such as a vessel or record) is associated with a specific ship name.
-
D.
associatedWithShipbuilder
Indicates a relationship where an entity is connected or linked in some relevant capacity to a shipbuilder.
-
E.
associatedWithVoyage
Indicates a relationship where an entity is linked or connected to a specific voyage, journey, or trip.
- 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_69e7ab322db0819092d6a2b3d4572e01 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69fdbaa226708190b8ed96e93aad38de |
completed | May 8, 2026, 10:27 a.m. |
| PD | Predicate disambiguation | batch_69fdb58b07e48190837e00966de050d4 |
completed | May 8, 2026, 10:06 a.m. |
Created at: April 22, 2026, 5:08 a.m.