Triple
T15688576
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Logo |
E380264
|
entity |
| Predicate | graphicsModel |
P94310
|
FINISHED |
| Object | vector-style line drawing |
—
|
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: vector-style line drawing | Statement: [Logo, graphicsModel, vector-style line drawing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: graphicsModel Context triple: [Logo, graphicsModel, vector-style line drawing]
-
A.
drawingModel
chosen
Indicates that one entity serves as a drawing or visual representation model used to depict, design, or illustrate another entity.
-
B.
designModel
Indicates that one entity creates, specifies, or defines the structure or behavior of another entity as a model or blueprint.
-
C.
has3DModels
Indicates that an entity is associated with one or more three-dimensional (3D) digital models representing it.
-
D.
onboardGraphicsModel
Indicates that an entity has a specific integrated or built-in graphics hardware model associated with it.
-
E.
hasShapeModel
Indicates that an entity is associated with a specific geometric or structural shape model that represents its form.
- 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_69d86d99e860819094b6957cde470f2c |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e04f4cee5481908699fbb2b7bdd2f6 |
completed | April 16, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69deda8c856c8190882330114f9a1a5f |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:44 a.m.