Triple
T7893156
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jekyll |
E183285
|
entity |
| Predicate | usesBuildModel |
P37433
|
FINISHED |
| Object | static site generation |
—
|
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: static site generation | Statement: [Jekyll, usesBuildModel, static site generation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesBuildModel Context triple: [Jekyll, usesBuildModel, static site generation]
-
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.
usesProductionModel
Indicates that one entity employs or relies on another entity as its primary or official production model in practice.
-
C.
builderModelCode
Indicates that one entity is identified as the specific model code used by a builder or construction-related system for another entity.
-
D.
useOfModel
chosen
Indicates that one entity employs, applies, or relies on a particular model for a specific purpose or task.
-
E.
usedByModel
Indicates that something (such as a resource, method, or component) is utilized or consumed by a particular model.
- 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_69ca828c474c8190a254d6499871eaff |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3a008fb88190a039fec40483ab93 |
completed | March 31, 2026, 3:05 a.m. |
| PD | Predicate disambiguation | batch_69cae92b0cd881908e715a10d3252e83 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5 p.m.