Triple
T9399477
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SS Botany Bay |
E226430
|
entity |
| Predicate | crewComplementType |
P88726
|
FINISHED |
| Object | genetically engineered superhumans |
—
|
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: genetically engineered superhumans | Statement: [SS Botany Bay, crewComplementType, genetically engineered superhumans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crewComplementType Context triple: [SS Botany Bay, crewComplementType, genetically engineered superhumans]
-
A.
crewType
Indicates the specific role or category of crew associated with an entity, such as the type of personnel assigned to operate or support it.
-
B.
crew
Indicates that one entity serves as the group of people who operate, staff, or work on another entity (such as a vehicle, vessel, or production).
-
C.
crewCount
Indicates the number of crew members associated with an entity, such as a vehicle, vessel, or mission.
-
D.
crewVariantName
Indicates the specific name or label assigned to a particular variant or version of a crew configuration.
-
E.
crewStatus
Indicates the current operational or role-related condition of a crew member or crew group within a mission or organization.
- 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_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. |
| PDg | Predicate description generation | batch_69cca89b3368819087a3d69270c1f185 |
completed | April 1, 2026, 5:09 a.m. |
Created at: March 30, 2026, 7:46 p.m.