Triple
T7893150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jekyll |
E183285
|
entity |
| Predicate | usesTemplateLanguage |
P2177
|
FINISHED |
| Object | Liquid |
—
|
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: Liquid | Statement: [Jekyll, usesTemplateLanguage, Liquid]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesTemplateLanguage Context triple: [Jekyll, usesTemplateLanguage, Liquid]
-
A.
usesLanguageRuntime
Indicates that an entity operates using, depends on, or is executed within a specific language runtime environment.
-
B.
scriptUsedForLanguage
Indicates that a particular writing script is employed to write or represent a given language.
-
C.
includesLanguage
chosen
Indicates that one entity contains, supports, or makes use of a specified language as part of its content, functionality, or representation.
-
D.
supportsLanguageOverrides
Indicates that an entity allows its default behavior or settings to be modified based on specific language selections or preferences.
-
E.
hasLanguageContext
Indicates that an entity is associated with or interpreted within a specific language or linguistic context.
- 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.