Triple
T14111980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Artemision Bronze |
E339659
|
entity |
| Predicate | legPosition |
P22528
|
FINISHED |
| Object | weight on rear leg |
—
|
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: weight on rear leg | Statement: [Artemision Bronze, legPosition, weight on rear leg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legPosition Context triple: [Artemision Bronze, legPosition, weight on rear leg]
-
A.
legOrientation
chosen
Indicates the relative positioning or directional alignment of an entity’s leg(s) with respect to a reference frame or another object.
-
B.
positionInArms
Indicates that one entity is being held or carried within the arms of another entity.
-
C.
legOrder
Indicates the sequential position or ordering of a specific leg within a multi-leg structure, process, or route.
-
D.
legs
Indicates that an entity possesses legs, specifying the presence or number of leg-like appendages associated with it.
-
E.
ridingPosition
Indicates the relative physical placement or posture of an entity while it is riding or being carried by 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_69d81c6a95b481909e39111e0c1f31ee |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de600e6a688190a1243a30ae9b7157 |
completed | April 14, 2026, 3:41 p.m. |
| PD | Predicate disambiguation | batch_69de05b2f7e481908a9a7d40153234c0 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:22 p.m.