Triple
T8917266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mushhushshu |
E212322
|
entity |
| Predicate | movementDepiction |
P46051
|
FINISHED |
| Object | shown striding forward |
—
|
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: shown striding forward | Statement: [Mushhushshu, movementDepiction, shown striding forward]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: movementDepiction Context triple: [Mushhushshu, movementDepiction, shown striding forward]
-
A.
movementDepicted
chosen
Indicates that some form of motion or change in position is visually represented or illustrated.
-
B.
describesMovement
Indicates that an entity undergoes or performs a change of position or location, capturing how it moves from one place or state to another.
-
C.
movementRepresentedBy
Indicates that a movement or motion of an entity is depicted, encoded, or symbolized by another entity (such as a sign, pattern, or representation).
-
D.
depictionAction
Indicates an action in which one entity visually represents, illustrates, or portrays another entity.
-
E.
movementType
Indicates the manner or mode in which an entity moves or is moved from one place or state to another.
- 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_69ca8393b1808190bd4336787ffa2c40 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6610cd48819090a184c5f9465626 |
completed | April 1, 2026, 12:25 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed0ef3c81908cc69eac852ee12a |
completed | March 31, 2026, 11:54 p.m. |
Created at: March 30, 2026, 6:56 p.m.