Triple
T23363713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mario Zucchelli Station |
E593252
|
entity |
| Predicate | supplyMode |
P152430
|
FINISHED |
| Object | ship resupply |
—
|
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: ship resupply | Statement: [Mario Zucchelli Station, supplyMode, ship resupply]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supplyMode Context triple: [Mario Zucchelli Station, supplyMode, ship resupply]
-
A.
supplyType
Indicates the kind or category of supply associated with or provided in a given relationship or context.
-
B.
supplyBy
Indicates that one entity is provided, furnished, or made available by another entity as its source or supplier.
-
C.
supplyRole
Indicates that an entity provides or fulfills a specific role within a supply or provisioning relationship to another entity.
-
D.
supplySituation
Indicates a relationship where one entity provides or makes available needed resources, goods, or services to another under specific conditions or circumstances.
-
E.
supplyPort
Indicates that one entity serves as a source or interface through which resources, materials, or energy are provided to 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_69e25d2593c88190bcdf4a716a94ccb2 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1a0aac4248190a4663ed12aed6856 |
completed | April 29, 2026, 6:09 a.m. |
| PD | Predicate disambiguation | batch_69f061c7aaa48190a58ce93f87155ffc |
completed | April 28, 2026, 7:29 a.m. |
| PDg | Predicate description generation | batch_69f0bd4a0e408190ad8916faf23562d9 |
completed | April 28, 2026, 1:59 p.m. |
Created at: April 17, 2026, 5:31 p.m.