Triple
T192890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SVG |
E3757
|
entity |
| Predicate | version |
P3286
|
FINISHED |
| Object | SVG Tiny |
E3757
|
NE 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: SVG Tiny | Statement: [SVG, version, SVG Tiny]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SVG Tiny Context triple: [SVG, version, SVG Tiny]
-
A.
SVG
chosen
SVG (Scalable Vector Graphics) is an XML-based vector image format for two-dimensional graphics that supports interactivity and animation, widely used for web graphics due to its scalability and resolution independence.
-
B.
Plotly
Plotly is an interactive, open-source graphing and data visualization library widely used in Python for creating rich, web-based charts and dashboards.
-
C.
SGML
SGML (Standard Generalized Markup Language) is a standardized metalanguage for defining markup languages used to structure and describe the content of electronic documents.
-
D.
XML
XML (Extensible Markup Language) is a flexible, text-based markup language designed for structuring, storing, and transporting data in a platform-independent way.
-
E.
Svelte
Svelte is a modern JavaScript framework and compiler for building user interfaces that shifts much of the work to a build step, producing highly efficient, minimal runtime code.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69a2548debd48190ae3a06d6e65b53c6 |
completed | Feb. 28, 2026, 2:35 a.m. |
| NER | Named-entity recognition | batch_69a259669ba08190a5be1d2e10e70b27 |
completed | Feb. 28, 2026, 2:56 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a31c91b22c8190a1d04983ae4fd793 |
completed | Feb. 28, 2026, 4:49 p.m. |
Created at: Feb. 28, 2026, 2:41 a.m.