Triple
T14868724
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Street Parade |
E349683
|
entity |
| Predicate | transportElement |
P53674
|
FINISHED |
| Object | trucks equipped with sound systems |
—
|
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: trucks equipped with sound systems | Statement: [Street Parade, transportElement, trucks equipped with sound systems]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transportElement Context triple: [Street Parade, transportElement, trucks equipped with sound systems]
-
A.
transportFrom
Indicates that something or someone is moved or carried away starting from a specified origin location.
-
B.
transportInterface
chosen
Indicates a relationship where one entity serves as the medium or mechanism through which another entity is transported or conveyed.
-
C.
transportedOver
Indicates that something is moved or carried across or along a specified medium, route, or surface.
-
D.
materialTransportedTo
Indicates that a material is moved or conveyed from one location or entity to another specified destination.
-
E.
canBeTransportedOver
Indicates that one entity is capable of being moved or carried across, along, or by means of another entity or medium.
- 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_69d822ee4f408190b6ac3b2fa434f0df |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69ded5776b848190bfe3a06ff261dc31 |
completed | April 15, 2026, 12:01 a.m. |
| PD | Predicate disambiguation | batch_69de8c1798c08190b433e9ad21e41a42 |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:55 a.m.