Triple
T22374963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | koa-static |
E553129
|
entity |
| Predicate | servesFileTypes |
P105373
|
FINISHED |
| Object | HTML |
—
|
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: HTML | Statement: [koa-static, servesFileTypes, HTML]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesFileTypes Context triple: [koa-static, servesFileTypes, HTML]
-
A.
typicalFileType
Indicates that one entity is the usual or commonly associated file type for the other entity.
-
B.
fileTypeCode
Indicates the specific classification or category code that identifies the type or format of a file.
-
C.
typicalFileFormat
chosen
Indicates the usual or standard file format typically associated with or used for a given entity or context.
-
D.
mediaTypeAvailable
Indicates that a particular type or format of media is available for use, access, or distribution in the given context.
-
E.
servesDestinationType
Indicates that an entity provides service to, or is intended for use with, a specific type or category of destination.
- 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_69e11e4c03248190a26a5060ea6973ee |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15807cb748190abd9adc08ca1ad4f |
completed | April 29, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69e73011e6388190a05edf137f488441 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:45 p.m.