Triple
T30370100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interoperable Master Format |
E772523
|
entity |
| Predicate | usesMetadata |
P163534
|
FINISHED |
| Object | XML |
—
|
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: XML | Statement: [Interoperable Master Format, usesMetadata, XML]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesMetadata Context triple: [Interoperable Master Format, usesMetadata, XML]
-
A.
hasMetadata
Indicates that one entity is associated with descriptive or informational data about another entity.
-
B.
dynamicMetadataSupport
Indicates that the subject system or component is capable of handling metadata that can change or be updated at runtime rather than being fixed or static.
-
C.
isMetadataOnly
Indicates that the referenced item exists solely as descriptive or structural metadata and does not include the actual underlying content or data.
-
D.
isMetadataAttribute
Indicates that one entity functions as a metadata attribute describing or qualifying another entity.
-
E.
metadata
chosen
Indicates that one entity provides descriptive or contextual information about another entity, such as its properties, origin, or structure.
- 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_69f2248d71408190aec0d5c2001b1cff |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7431c0eec81909ead443e07d75e18 |
completed | May 3, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69f74143cf708190a12d487884298437 |
completed | May 3, 2026, 12:36 p.m. |
Created at: April 29, 2026, 7:59 p.m.