Triple
T20070199
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dumont d’Urville Station |
E499711
|
entity |
| Predicate | supplyBy |
P138584
|
FINISHED |
| Object | ice-strengthened research vessel |
—
|
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: ice-strengthened research vessel | Statement: [Dumont d’Urville Station, supplyBy, ice-strengthened research vessel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supplyBy Context triple: [Dumont d’Urville Station, supplyBy, ice-strengthened research vessel]
-
A.
supplyType
Indicates the kind or category of supply associated with or provided in a given relationship or context.
-
B.
supplyRole
Indicates that an entity provides or fulfills a specific role within a supply or provisioning relationship to another entity.
-
C.
supplySituation
Indicates a relationship where one entity provides or makes available needed resources, goods, or services to another under specific conditions or circumstances.
-
D.
suppliesTo
Indicates that one entity provides or delivers goods, services, or resources to another entity.
-
E.
supplyCut
Indicates that the normal provision or flow of a resource, product, or service to an entity has been reduced, interrupted, or stopped.
- 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_69da627770948190997f486f9a2e370f |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6643798a4819081fa4e71c74b47bc |
completed | April 20, 2026, 5:36 p.m. |
| PD | Predicate disambiguation | batch_69e54cee7a5c819084ae4ff26419833f |
completed | April 19, 2026, 9:45 p.m. |
| PDg | Predicate description generation | batch_69e54fc20888819083c9118a09d0d2dc |
completed | April 19, 2026, 9:57 p.m. |
Created at: April 11, 2026, 3:40 p.m.