Triple
T17519692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OpenAPI Generator |
E426652
|
entity |
| Predicate | streamlines |
P127761
|
FINISHED |
| Object | API development |
—
|
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: API development | Statement: [OpenAPI Generator, streamlines, API development]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: streamlines Context triple: [OpenAPI Generator, streamlines, API development]
-
A.
streams
Indicates that one entity continuously transmits or delivers data, media, or content in real time to another entity.
-
B.
lining
Indicates that one entity forms a layer or covering along the inner or outer surface of another entity.
-
C.
flowsParallelTo
Indicates that one entity moves or extends in the same direction as another without intersecting it, maintaining a parallel course.
-
D.
flowsThroughLandscape
Indicates that something (typically a fluid or moving entity) passes through or traverses a particular landscape or terrain.
-
E.
flowsBeside
Indicates that one entity moves or runs alongside another entity in close proximity without crossing or intersecting it.
- 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_69d889de677081909b22d2657b1f0292 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e452d18c1c81908bb843bbddb44ca1 |
completed | April 19, 2026, 3:58 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f8b9888190aa8a45e09acf4319 |
completed | April 18, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69e3bbb37d148190b7f38599c06594ee |
completed | April 18, 2026, 5:13 p.m. |
Created at: April 10, 2026, 5:49 a.m.