Triple
T13109747
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shy Guy |
E310937
|
entity |
| Predicate | designTrait |
P57584
|
FINISHED |
| Object | simple silhouette |
—
|
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: simple silhouette | Statement: [Shy Guy, designTrait, simple silhouette]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designTrait Context triple: [Shy Guy, designTrait, simple silhouette]
-
A.
designedFeature
chosen
Indicates that one entity is a feature or component intentionally planned, created, or specified by another entity as part of a design.
-
B.
designMethod
Indicates that one entity is used as the method, approach, or technique by which another entity is designed or created.
-
C.
designDescription
Indicates that an entity has a textual explanation or summary of its design, structure, or intended configuration.
-
D.
designUse
Indicates that one entity is used as a design basis, purpose, or intended functional use for another entity.
-
E.
designClass
Indicates that one entity is the design or blueprint class from which the other entity is derived or instantiated.
- 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_69d806a872d08190a329806f8ff30df4 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d9817e4f408190b77c198b4157d77a |
completed | April 10, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69d98041a3548190a05ddd83dbb660fa |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9:05 p.m.