Triple
T1097291
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blue Eagle |
E24297
|
entity |
| Predicate | visualElement |
P11599
|
FINISHED |
| Object | spread wings |
—
|
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: spread wings | Statement: [Blue Eagle, visualElement, spread wings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: visualElement Context triple: [Blue Eagle, visualElement, spread wings]
-
A.
visualizationLibrary
Indicates that an entity uses, depends on, or is implemented with a particular visualization library for rendering or displaying visual data.
-
B.
plotElement
Indicates that one entity functions as a narrative component or structural element within the storyline of another entity (such as a work of fiction or media).
-
C.
visualForm
chosen
Indicates the visual appearance, shape, or structural pattern that characterizes how something looks.
-
D.
graphics
Indicates a relationship where one entity is responsible for creating, providing, or handling visual representations or graphical content for another entity or context.
-
E.
visualEffect
Indicates that one entity produces, modifies, or is associated with a particular visual effect on another entity or within a scene.
- 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_69a4940542308190ac2a0b1f730b7cfc |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4b9a1d3108190b2a304fef429848d |
completed | March 1, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69a4b7448c148190a3c9a4158ebd05b4 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.