Triple
T23792578
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Listen to Your Heartbeat |
E588442
|
entity |
| Predicate | performedInRunningOrderPosition |
P86740
|
FINISHED |
| Object | 4 |
—
|
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: 4 | Statement: [Listen to Your Heartbeat, performedInRunningOrderPosition, 4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performedInRunningOrderPosition Context triple: [Listen to Your Heartbeat, performedInRunningOrderPosition, 4]
-
A.
performedInNumber
Indicates that an action or event was carried out a specified number of times.
-
B.
performerPosition
Indicates the spatial or role-based placement of a performer relative to a performance context or other participants.
-
C.
positionInPerformance
chosen
Indicates the specific ordering or placement of an entity within a performance or sequence of performed elements.
-
D.
positionInRound
Indicates the specific ordinal place an entity occupies within a given round or sequence of rounds.
-
E.
positionInJudgesSequence
Indicates the specific ordinal place that a judge occupies within an ordered sequence of judges.
- 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_69e25d15db58819092ac1e6791696fd9 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c6d939c08190997246abe5781b83 |
completed | April 29, 2026, 8:52 a.m. |
| PD | Predicate disambiguation | batch_69f155fe300481909bd617443228df65 |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:36 p.m.