Triple
T9399488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SS Botany Bay |
E226430
|
entity |
| Predicate | crewStatusAtDiscovery |
P51184
|
FINISHED |
| Object | in suspended animation |
—
|
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: in suspended animation | Statement: [SS Botany Bay, crewStatusAtDiscovery, in suspended animation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crewStatusAtDiscovery Context triple: [SS Botany Bay, crewStatusAtDiscovery, in suspended animation]
-
A.
crewStatus
chosen
Indicates the current operational or role-related condition of a crew member or crew group within a mission or organization.
-
B.
firstCrewBoarded
Indicates that the initial group of crew members has boarded or entered a specified vehicle, vessel, or location.
-
C.
firstCrewMember
Indicates that the subject is the first (earliest or primary) member within a specified crew or group.
-
D.
causeOfDiscovery
Indicates that one entity is the reason or factor that led to the discovery of another entity.
-
E.
shipAtTimeOfDisappearance
Indicates that a particular ship is associated with the specific time at which it disappeared.
- 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_69ca843170f88190800a8ab2b5fc568e |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd51556fc08190b8ff8190a1485a3a |
completed | April 1, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69cca545b2448190a4297312e39c21ac |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:46 p.m.