Triple
T27878807
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Back to the Bar |
E705029
|
entity |
| Predicate | featuresFollowUpsTo |
P32415
|
FINISHED |
| Object | bars previously featured on Bar Rescue |
—
|
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: bars previously featured on Bar Rescue | Statement: [Back to the Bar, featuresFollowUpsTo, bars previously featured on Bar Rescue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresFollowUpsTo Context triple: [Back to the Bar, featuresFollowUpsTo, bars previously featured on Bar Rescue]
-
A.
followsUp
chosen
Indicates that one entity continues, responds to, or builds upon a previous entity, typically as a subsequent action, communication, or step.
-
B.
followUpType
Indicates the specific category or nature of a follow-up action or interaction that occurs after an initial event or communication.
-
C.
followsTo
Indicates that one entity moves or proceeds behind another entity toward a specific destination or target.
-
D.
followsBy
Indicates that one event, state, or entity occurs or comes immediately after another in a sequence or order.
-
E.
followUpNeeded
Indicates that an additional action, check, or communication is required after an initial event or interaction.
- 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_69ef84111bb4819084298f994b31c62f |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69fdbaa226708190b8ed96e93aad38de |
completed | May 8, 2026, 10:27 a.m. |
| PD | Predicate disambiguation | batch_69fdb58b07e48190837e00966de050d4 |
completed | May 8, 2026, 10:06 a.m. |
Created at: April 27, 2026, 6:29 p.m.