Triple
T22650117
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JSX |
E559068
|
entity |
| Predicate | syntaxInspiredBy |
P5327
|
FINISHED |
| Object | HTML |
—
|
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: HTML | Statement: [JSX, syntaxInspiredBy, HTML]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: syntaxInspiredBy Context triple: [JSX, syntaxInspiredBy, HTML]
-
A.
syntaxBasedOn
chosen
Indicates that the syntactic structure or rules of one entity are derived from, influenced by, or constructed according to the syntax of another entity.
-
B.
syntaxStyle
Indicates the stylistic or structural conventions used in the form or arrangement of an expression, statement, or code.
-
C.
syntaxFamily
Indicates that two linguistic elements share a common syntactic type, pattern, or structural classification within a grammar system.
-
D.
syntaxElement
Indicates a relationship where something functions as a syntactic unit or component within a larger grammatical or structural expression.
-
E.
notationLanguage
Indicates the language or symbolic system in which a notation or formal representation is expressed.
- 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_69e245489dd88190b1f674acf61c8769 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1703b40b88190aec5cf2fa28bfcbf |
completed | April 29, 2026, 2:43 a.m. |
| PD | Predicate disambiguation | batch_69ee6294c4c08190b7e4829f4b9af24b |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:05 p.m.