Triple
T22375023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | koa-logger |
E553130
|
entity |
| Predicate | loggingLevel |
P147414
|
FINISHED |
| Object | request-level logging |
—
|
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: request-level logging | Statement: [koa-logger, loggingLevel, request-level logging]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: loggingLevel Context triple: [koa-logger, loggingLevel, request-level logging]
-
A.
loggingMode
Indicates the configuration or method by which events, actions, or data are recorded in logs.
-
B.
logicalLevel
Indicates the relative position or depth of something within a hierarchy of abstraction, reasoning, or logical structure.
-
C.
configurationLevel
Indicates the degree or tier of settings or parameters applied to configure something within a system or context.
-
D.
exportLevel
Indicates the degree or extent to which something is produced in one place and sent out or made available to other places or markets.
-
E.
loggingLocation
Indicates the place or destination where logs or logging information are recorded or stored.
- 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_69f15807cb748190abd9adc08ca1ad4f |
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.