Triple
T6459750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pram Race (Oxted) |
E142086
|
entity |
| Predicate | typicalTransportObject |
P71117
|
FINISHED |
| Object | pram |
—
|
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: pram | Statement: [Pram Race (Oxted), typicalTransportObject, pram]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalTransportObject Context triple: [Pram Race (Oxted), typicalTransportObject, pram]
-
A.
usesTransport
Indicates that an entity employs or relies on a particular mode or means of transportation to move from one place to another.
-
B.
transportInterface
Indicates a relationship where one entity serves as the medium or mechanism through which another entity is transported or conveyed.
-
C.
transportFrom
Indicates that something or someone is moved or carried away starting from a specified origin location.
-
D.
transportAgnostic
Indicates that the relationship or action is independent of, and unaffected by, the specific transport mechanism or communication channel used.
-
E.
transportedOver
Indicates that something is moved or carried across or along a specified medium, route, or surface.
- F. None of above. chosen
Provenance (4 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_69c008d2f91c8190a8178767a35e08fc |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c069f347f48190a2b22c5b648b17bd |
completed | March 22, 2026, 10:15 p.m. |
| PD | Predicate disambiguation | batch_69c0673b44148190aed70084f0ff4992 |
completed | March 22, 2026, 10:03 p.m. |
| PDg | Predicate description generation | batch_69c068cb3b888190812ed56f2fdd45ed |
completed | March 22, 2026, 10:10 p.m. |
Created at: March 22, 2026, 4:48 p.m.