Triple
T29430073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VHF DSC |
E746402
|
entity |
| Predicate | requiresIdentifier |
P100200
|
FINISHED |
| Object | Maritime Mobile Service Identity |
—
|
NE NERFINISHED |
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: Maritime Mobile Service Identity | Statement: [VHF DSC, requiresIdentifier, Maritime Mobile Service Identity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresIdentifier Context triple: [VHF DSC, requiresIdentifier, Maritime Mobile Service Identity]
-
A.
haveIdentifier
Indicates that an entity is associated with a specific identifier used to uniquely reference or distinguish it.
-
B.
identifierFor
Indicates that one entity serves as a unique identifying label or code for another entity.
-
C.
supportsIdentifierType
chosen
Indicates that one entity is capable of recognizing, handling, or working with a specified type or format of identifier.
-
D.
requiresStatement
Indicates that one entity necessitates the presence, provision, or assertion of a specific statement from another entity in order for some condition, process, or relation to hold.
-
E.
requiresReferent
Indicates that one entity depends on or must reference another specific entity in order to be valid, interpretable, or complete.
- 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_69f0a7a06e0081908add494075912eb4 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69fd7b0503a08190ba07338365b6fcc9 |
completed | May 8, 2026, 5:56 a.m. |
| PD | Predicate disambiguation | batch_69fd7a9733dc81909199f453c0cc2bc1 |
completed | May 8, 2026, 5:54 a.m. |
Created at: April 28, 2026, 3:12 p.m.