Triple
T29607272
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | urql |
E754606
|
entity |
| Predicate | supportsDevtools |
P105440
|
FINISHED |
| Object | browser devtools extension |
—
|
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: browser devtools extension | Statement: [urql, supportsDevtools, browser devtools extension]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsDevtools Context triple: [urql, supportsDevtools, browser devtools extension]
-
A.
supportsDebuggingTools
chosen
Indicates that an entity provides or is compatible with tools used for debugging or diagnosing issues.
-
B.
supportsDeviceChaining
Indicates that one device can be connected in sequence with others, allowing multiple devices to operate together in a chained configuration.
-
C.
supportsDeveloper
Indicates that one entity provides assistance, resources, or advocacy to help a developer perform their work or achieve their goals.
-
D.
supportsCloudTesting
Indicates that one entity provides or enables cloud-based testing capabilities for another entity or process.
-
E.
hasDevelopmentDriver
Indicates that one entity serves as a driving factor, cause, or motivator for the development, growth, or advancement of 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_69f0ef84e5d08190a0df17f5930ceed3 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e0f3d88190a4ee7b0673f1ef90 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 28, 2026, 6:26 p.m.