Triple
T578137
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO 15022 |
E15000
|
entity |
| Predicate | hasFormatType |
P8462
|
FINISHED |
| Object | tagged data fields |
—
|
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: tagged data fields | Statement: [ISO 15022, hasFormatType, tagged data fields]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFormatType Context triple: [ISO 15022, hasFormatType, tagged data fields]
-
A.
hasFileFormat
chosen
Indicates that one entity (typically a digital file or resource) is encoded, stored, or represented using a specific file format defined by the other entity.
-
B.
hasFormulationType
Indicates the specific way something is physically prepared or presented, such as its dosage form, composition, or delivery format.
-
C.
hasForm
Indicates that one entity possesses, exhibits, or is characterized by a particular shape, structure, or configuration.
-
D.
hasStructureType
Indicates that an entity possesses or is classified by a specific structural type or configuration.
-
E.
hasPropertyType
Indicates that an entity possesses or is associated with a specific type or category of property.
- 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_69a4935783b8819082b77726ec10cc42 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49b69fed88190b5558d4ebd5047a1 |
completed | March 1, 2026, 8:02 p.m. |
| PD | Predicate disambiguation | batch_69a494c692288190b88f30299516b5ba |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:33 p.m.