Triple
T22374706
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Koa |
E553123
|
entity |
| Predicate | firstClassFeature |
P147412
|
FINISHED |
| Object | async middleware functions |
—
|
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: async middleware functions | Statement: [Koa, firstClassFeature, async middleware functions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstClassFeature Context triple: [Koa, firstClassFeature, async middleware functions]
-
A.
firstToFeature
Indicates that one entity was the earliest or initial subject to exhibit, include, or present another entity in a given context.
-
B.
firstClassRuns
Indicates that the subject has participated in official first-class cricket matches, with the object specifying the number or record of such runs scored.
-
C.
primaryClass
Indicates that one entity is the main or principal classification category to which another entity belongs.
-
D.
firstFirstClassMatch
Indicates that the referenced match is the earliest (chronologically first) match classified as a first-class match for the given context or entity.
-
E.
firstStandard
Indicates that the subject is the earliest or primary instance in a defined standard, sequence, or set of reference criteria.
- F. None of above. chosen
Provenance (4 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_69f15806b534819083716c2b090ede42 |
completed | April 29, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69e73011e6388190a05edf137f488441 |
completed | April 21, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e7342e9a0081909257210a81c96b29 |
completed | April 21, 2026, 8:24 a.m. |
Created at: April 16, 2026, 8:45 p.m.