Triple
T36236258
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nunjucks |
E891384
|
entity |
| Predicate | supportsDataContext |
P148413
|
FINISHED |
| Object | JSON data |
—
|
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: JSON data | Statement: [Nunjucks, supportsDataContext, JSON data]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsDataContext Context triple: [Nunjucks, supportsDataContext, JSON data]
-
A.
dataContext
Indicates the situational or environmental conditions under which data is produced, interpreted, or used, such as source, scope, assumptions, and relevant constraints.
-
B.
supportsDataBinding
chosen
Indicates that one entity enables or is compatible with automatic synchronization of data values between sources and targets (data binding) in another entity.
-
C.
supportsDataRegion
Indicates that one entity is capable of operating with, storing, or otherwise handling data that resides in a specified geographic or logical data region.
-
D.
supportsDataFrom
Indicates that one entity provides, validates, or underpins the data used or referenced by another entity.
-
E.
dataSupports
Indicates that one piece of data provides evidence, justification, or backing for the validity or reliability of another piece of data, claim, or conclusion.
- 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_69f76e4387048190a1b27bcbf4ec7423 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0a54cc8190868c1bfa1590d1a6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:09 p.m.