Triple
T37676221
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wilson A2K |
E938100
|
entity |
| Predicate | positionVariants |
P33537
|
FINISHED |
| Object | infield gloves |
—
|
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: infield gloves | Statement: [Wilson A2K, positionVariants, infield gloves]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionVariants Context triple: [Wilson A2K, positionVariants, infield gloves]
-
A.
positions
Indicates that one entity assigns, arranges, or places another entity in a specific location, role, or order relative to others.
-
B.
displacementVariant
chosen
Indicates a relationship where one entity is an alternative or modified form of another that differs specifically in its spatial position or displacement.
-
C.
possiblePosition
Indicates that a given location or arrangement is a valid or allowable position for the entity within the specified context or constraints.
-
D.
positionInCase
Indicates the specific role, status, or placement that an entity holds within a particular case or legal proceeding.
-
E.
positionB
Indicates that one entity occupies or is located at a specific position relative to 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_69f76ed7b1408190ba8c93c53cb8becf |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ffe613c03481909f3043ec8bf0bed9 |
completed | May 10, 2026, 1:57 a.m. |
| PD | Predicate disambiguation | batch_69ffe4a73fb4819091600725a443981a |
completed | May 10, 2026, 1:51 a.m. |
Created at: May 3, 2026, 4:18 p.m.