Triple
T37067664
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port of Genk |
E917491
|
entity |
| Predicate | isMultimodal |
P25869
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Port of Genk, isMultimodal, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMultimodal Context triple: [Port of Genk, isMultimodal, true]
-
A.
hadMultiModalUse
Indicates that something was used in multiple modes, formats, or modalities rather than in a single, uniform way.
-
B.
modalityOf
Indicates that one element specifies the manner, mood, or mode in which the action, event, or state expressed by another element is realized or presented.
-
C.
isMultiPurpose
Indicates that something is designed or used to serve multiple functions or purposes rather than a single, specialized one.
-
D.
usesModality
chosen
Indicates that an action, communication, or process is carried out through or characterized by a particular modality (such as visual, auditory, tactile, or another mode of expression or operation).
-
E.
isModular
Indicates that something is composed of distinct, interchangeable parts or units that can be independently created, modified, or replaced within a larger whole.
- 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_69f76e95fa40819091e14681087ae5e4 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb34e5576881909394355c8ec6ddd2 |
completed | May 6, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69fb2f6171e88190bf1e0ee6a644b6a9 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:14 p.m.