Triple
T4554261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Walk On By |
E120443
|
entity |
| Predicate | hasBeenWidelyCovered |
P37383
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Walk On By, hasBeenWidelyCovered, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBeenWidelyCovered Context triple: [Walk On By, hasBeenWidelyCovered, true]
-
A.
hasPublisherCoverage
Indicates that a publisher provides content, services, or distribution that extend over or apply to a specified entity or area.
-
B.
isFrequentlyCovered
chosen
Indicates that an entity is regularly or commonly reported on, discussed, or featured, especially in media or informational sources.
-
C.
hasBroadcastCoverageIn
Indicates that a broadcast (such as a TV or radio program, channel, or signal) is available or transmitted within a specified geographic area or region.
-
D.
mediaCovered
Indicates that one entity (such as a media outlet or source) has reported on, featured, or otherwise provided coverage of another entity or event.
-
E.
mediaCoverage
Indicates that one entity reports on, documents, or broadcasts information about another entity through news or media channels.
- 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_69bd4636f1648190a701445c2fcd9c17 |
completed | March 20, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69bd58127ed08190a04962a43afb888b |
completed | March 20, 2026, 2:22 p.m. |
| PD | Predicate disambiguation | batch_69bd5223423c81908317351b58cff5f5 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:09 p.m.