Triple
T21228492
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PS-2 covered hopper |
E523142
|
entity |
| Predicate | protectsCargoFrom |
P20171
|
FINISHED |
| Object | rain |
—
|
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: rain | Statement: [PS-2 covered hopper, protectsCargoFrom, rain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: protectsCargoFrom Context triple: [PS-2 covered hopper, protectsCargoFrom, rain]
-
A.
primaryCargoProtected
Indicates that the main cargo associated with an entity is safeguarded or shielded from harm, loss, or interference.
-
B.
protectsShippingTo
Indicates that one entity safeguards or ensures the security of shipping or delivery directed toward another entity.
-
C.
protects
Indicates taking action to keep someone or something safe from harm, danger, or negative effects.
-
D.
mainCargo
Indicates that one entity serves as the primary or principal cargo carried or transported by another entity.
-
E.
providesProtectionAgainst
chosen
Indicates that one entity serves to guard, shield, or defend another entity from a specified harm, threat, or adverse effect.
- 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_69e0b512ad94819087942b2ed925185f |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e734ad5068819088b203eeba4e6380 |
completed | April 21, 2026, 8:26 a.m. |
| PD | Predicate disambiguation | batch_69e5f60e1a888190ba75e2e900270a4e |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:44 p.m.