Triple
T18602597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anadyr seaport |
E454653
|
entity |
| Predicate | supportsTransportType |
P43182
|
FINISHED |
| Object | cargo ships |
—
|
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: cargo ships | Statement: [Anadyr seaport, supportsTransportType, cargo ships]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsTransportType Context triple: [Anadyr seaport, supportsTransportType, cargo ships]
-
A.
supportsTransportIntegrationWith
Indicates that one entity enables or is compatible with the integration of transport or transportation-related systems, services, or data with another entity.
-
B.
supportsDriverType
Indicates that one entity is compatible with, or able to operate using, a specified type of driver.
-
C.
supportsMobilityType
chosen
Indicates that one entity provides compatibility with, or can function using, a specified type of mobility or movement mode.
-
D.
transmissionTypeSupported
Indicates that a particular type of transmission is compatible with or can be used by a given system, device, or component.
-
E.
supportsType
Indicates that one entity is capable of handling, accepting, or being compatible with a specified type.
- 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_69d8d38bbe7c8190bdec3138e7d413c9 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e54751d7ec81909efc4867f649002e |
completed | April 19, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69e478cf5e888190a0b1074b0c6525df |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:45 a.m.