Triple
T13582817
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | J-bar |
E324463
|
entity |
| Predicate | loadMethod |
P41759
|
FINISHED |
| Object | riders position themselves and place bar behind body |
—
|
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: riders position themselves and place bar behind body | Statement: [J-bar, loadMethod, riders position themselves and place bar behind body]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: loadMethod Context triple: [J-bar, loadMethod, riders position themselves and place bar behind body]
-
A.
relocationMethod
Indicates the means or process by which something or someone is moved from one location to another.
-
B.
usesLaunchMethod
Indicates that one entity employs or applies a particular launch method to initiate or start another entity or process.
-
C.
loadType
chosen
Indicates the manner or category of how something is loaded, such as the method, configuration, or type of loading applied in a given context.
-
D.
transformerMethod
Indicates a method or function that performs a transformation from one form, state, or representation to another.
-
E.
method
Indicates the technique, procedure, or process used by an entity to perform an action or achieve a result.
- 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.