Triple
T8756207
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JSON5 |
E208077
|
entity |
| Predicate | mimetype |
P71607
|
FINISHED |
| Object | application/json5 |
—
|
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: application/json5 | Statement: [JSON5, mimetype, application/json5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mimetype Context triple: [JSON5, mimetype, application/json5]
-
A.
typicalMIMEType
Indicates the standard or most commonly used MIME (media) type associated with a given resource or format.
-
B.
mediaType
Indicates the format or category of media associated with an entity, such as text, image, audio, or video.
-
C.
MIMEName
chosen
Indicates the standardized MIME (Multipurpose Internet Mail Extensions) type name associated with a given entity, specifying its media type and subtype for content identification.
-
D.
fileTypeMasquerade
Indicates that a file is presented or labeled as one type while actually being of a different underlying type.
-
E.
metadataType
Indicates that one entity specifies the kind or category of metadata associated with another entity.
- 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_69ca835cd6b08190bd7c63db92f53c86 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5dd95e9481909cc88e8d91601754 |
completed | March 31, 2026, 11:50 p.m. |
| PD | Predicate disambiguation | batch_69cc5c160dac8190b4aeb4bf0529de52 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:40 p.m.