Triple
T10828103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Python logo with two snakes |
E255543
|
entity |
| Predicate | fileFormatAvailableAs |
P8462
|
FINISHED |
| Object | SVG |
—
|
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: SVG | Statement: [Python logo with two snakes, fileFormatAvailableAs, SVG]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fileFormatAvailableAs Context triple: [Python logo with two snakes, fileFormatAvailableAs, SVG]
-
A.
fileFormatStandard
Indicates that something conforms to, specifies, or defines a standardized structure and rules for how data is organized and stored in a file.
-
B.
operatesInFormat
Indicates that an entity functions, performs its role, or is carried out using a specified format.
-
C.
hasFileFormat
chosen
Indicates that one entity (typically a digital file or resource) is encoded, stored, or represented using a specific file format defined by the other entity.
-
D.
canExportToFormat
Indicates that something has the capability to be exported or converted into a specified file or data format.
-
E.
canBeSavedAs
Indicates that one entity is capable of being stored or preserved in the form or format of another entity.
- 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_69d6aa8081448190a9324184f2bd1c26 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d734d3eab88190b30a3025b6b2b0bc |
completed | April 9, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69d70d25280c8190b648d7d1958b413a |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:19 p.m.