Triple
T16692451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orb-1 |
E405627
|
entity |
| Predicate | cargoContents |
P124266
|
FINISHED |
| Object | crew supplies |
—
|
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: crew supplies | Statement: [Orb-1, cargoContents, crew supplies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cargoContents Context triple: [Orb-1, cargoContents, crew supplies]
-
A.
cargoLoading
Indicates the action or process of placing cargo onto a vehicle, vessel, or other transport medium for shipment or movement.
-
B.
cargoAccess
Indicates that an entity has permission or capability to access, enter, or interact with a cargo area or cargo-related contents.
-
C.
cargoSpace
Indicates that one entity provides storage capacity or room for carrying goods, equipment, or other items for another entity.
-
D.
cargoHoldType
Indicates the specific type or classification of a cargo hold associated with an entity.
-
E.
mainCargo
Indicates that one entity serves as the primary or principal cargo carried or transported by another entity.
- 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_69d8838c28748190b3f5967c743940ab |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37eaacb948190954231c9e97a4adf |
completed | April 18, 2026, 12:52 p.m. |
| PD | Predicate disambiguation | batch_69e319bc73908190a0e38bc926b31f10 |
completed | April 18, 2026, 5:42 a.m. |
| PDg | Predicate description generation | batch_69e326b9e84881909a9166e65bd850d6 |
completed | April 18, 2026, 6:37 a.m. |
Created at: April 10, 2026, 5:19 a.m.