Triple
T13582796
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | J-bar |
E324463
|
entity |
| Predicate | riderContact |
P19362
|
FINISHED |
| Object | bar placed behind legs or hips |
—
|
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: bar placed behind legs or hips | Statement: [J-bar, riderContact, bar placed behind legs or hips]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riderContact Context triple: [J-bar, riderContact, bar placed behind legs or hips]
-
A.
notableRiderType
Indicates that an entity is notably associated with a particular type or category of rider (e.g., cyclist, jockey, driver).
-
B.
riderType
Indicates the category or role of a rider in relation to a ride, transport service, or vehicle (e.g., passenger, driver, courier).
-
C.
managedRider
Indicates that one entity was responsible for directing, organizing, or overseeing the activities or career of a rider.
-
D.
famousRider
Indicates that an entity is a rider who is widely known or celebrated.
-
E.
contactWith
chosen
Indicates that two entities are in direct or indirect physical or communicative interaction or touch with each other.
- 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_69d80769100c819099111274614f5ed2 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbb031e8048190a5f2ea934308036c |
completed | April 12, 2026, 2:46 p.m. |
| PD | Predicate disambiguation | batch_69dbae161a0481909f9d3f40ca4e0ac5 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:49 p.m.