Triple
T38080317
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thunderstorm |
E950833
|
entity |
| Predicate | followedInOrderBy |
P50088
|
FINISHED |
| Object | fifth movement of Beethoven’s Sixth Symphony |
—
|
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: fifth movement of Beethoven’s Sixth Symphony | Statement: [Thunderstorm, followedInOrderBy, fifth movement of Beethoven’s Sixth Symphony]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followedInOrderBy Context triple: [Thunderstorm, followedInOrderBy, fifth movement of Beethoven’s Sixth Symphony]
-
A.
followedIn
Indicates that one entity began following or subscribing to another entity, typically in a social or sequential context.
-
B.
followsBy
chosen
Indicates that one event, state, or entity occurs or comes immediately after another in a sequence or order.
-
C.
followsIn
Indicates that one entity comes after or succeeds another in a sequence, order, or progression.
-
D.
followsOrderFrom
Indicates that one entity complies with and acts according to the instructions or commands issued by another entity.
-
E.
followsBetween
Indicates that one entity comes after or succeeds another entity within a specified context or sequence.
- 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_69f76f03a3608190a73fd6df87c792a8 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69ff9a25407c81909faa86e72a7a9d17 |
completed | May 9, 2026, 8:33 p.m. |
| PD | Predicate disambiguation | batch_69ff99c613688190a03b2f93d5ccad2b |
completed | May 9, 2026, 8:32 p.m. |
Created at: May 3, 2026, 4:21 p.m.