Triple
T14868727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Street Parade |
E349683
|
entity |
| Predicate | Love MobilesRole |
P23065
|
FINISHED |
| Object | core element of the parade |
—
|
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: core element of the parade | Statement: [Street Parade, Love MobilesRole, core element of the parade]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Love MobilesRole Context triple: [Street Parade, Love MobilesRole, core element of the parade]
-
A.
carrierOf
chosen
Indicates that one entity serves as the medium, vehicle, or host that contains, transports, or conveys another entity.
-
B.
cellularOptions
Indicates that one entity specifies or provides available cellular network or mobile connectivity options for another entity.
-
C.
deviceIndicates
Indicates that a device provides a signal, status, or output that conveys information about a condition, event, or state.
-
D.
deviceModel
Indicates the specific model designation associated with a device.
-
E.
featuresMobFamily
Indicates that something includes, portrays, or prominently involves a mob or mafia family as part of its content or structure.
- 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.