Triple
T4275861
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gulp |
E97045
|
entity |
| Predicate | buildProcessModel |
P38228
|
FINISHED |
| Object | stream-based |
—
|
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: stream-based | Statement: [Gulp, buildProcessModel, stream-based]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: buildProcessModel Context triple: [Gulp, buildProcessModel, stream-based]
-
A.
builderModel
Indicates a relationship where one entity serves as the design or construction template (the "builder model") used to create, configure, or generate another entity.
-
B.
definesProcessFor
chosen
Indicates that one entity specifies or establishes the process or procedure to be used for another entity.
-
C.
executionModel
Indicates how a process, task, or operation is carried out or implemented, specifying the underlying method, strategy, or mechanism of its execution.
-
D.
planningModelFor
Indicates that one entity serves as a planning model used to guide, simulate, or structure the planning activities related to another entity.
-
E.
basedOnProcess
Indicates that something is derived from, determined by, or dependent on a particular process or sequence of actions.
- 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_69b34544be3c819084d1ab82d29f90c5 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3501c35688190a7d15d904f15f968 |
completed | March 12, 2026, 11:45 p.m. |
| PD | Predicate disambiguation | batch_69b347faa45481908c19c29fb906dc92 |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:07 p.m.