Triple
T25764399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Blue Ghost |
E648838
|
entity |
| Predicate | appliedToShipStatus |
P134515
|
FINISHED |
| Object | repeatedly reported sunk |
—
|
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: repeatedly reported sunk | Statement: [The Blue Ghost, appliedToShipStatus, repeatedly reported sunk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliedToShipStatus Context triple: [The Blue Ghost, appliedToShipStatus, repeatedly reported sunk]
-
A.
appliesToShips
Indicates that the specified condition, rule, or attribute is relevant to or affects ships.
-
B.
appliedToStatus
chosen
Indicates that an action, rule, or condition is associated with or affects a particular status or state.
-
C.
hasShip
Indicates that one entity possesses, owns, or is equipped with a ship.
-
D.
shippingLaneStatus
Indicates the current operational condition or availability of a specified shipping lane for transit or navigation.
-
E.
stateShip
Indicates that a ship is officially registered, documented, or associated with a particular state or governmental authority.
- 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_69f68805b4848190b75da14996d52a38 |
completed | May 2, 2026, 11:25 p.m. |
| PD | Predicate disambiguation | batch_69f68609c0b08190a8e1238a4d97c270 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 22, 2026, 5:08 a.m.