Triple
T38387128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Menuet |
E899607
|
entity |
| Predicate | commonlyAppearsAs |
P24836
|
FINISHED |
| Object | third movement of symphonies |
—
|
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: third movement of symphonies | Statement: [Menuet, commonlyAppearsAs, third movement of symphonies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonlyAppearsAs Context triple: [Menuet, commonlyAppearsAs, third movement of symphonies]
-
A.
alsoAppearsAs
Indicates that an entity is known or presented under an alternative name, form, or representation.
-
B.
appearsAs
chosen
Indicates that one entity is presented, perceived, or manifested in the form, role, or guise of another entity.
-
C.
appearsInFullNameOf
Indicates that one entity (typically a string or term) occurs as a contiguous part within the complete name of another entity.
-
D.
oftenUsedAsNameFor
Indicates that something frequently serves as a name or designation for another entity.
-
E.
commonlyIdentifiedWith
Indicates that two entities are widely regarded or treated as the same or equivalent, even if they are formally distinct.
- 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_69f76e5c9b808190b486523f5c2f817d |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff79e7206c8190a809b5f2a6261378 |
completed | May 9, 2026, 6:16 p.m. |
| PD | Predicate disambiguation | batch_69ff798356b881908645074fb3a96517 |
completed | May 9, 2026, 6:14 p.m. |
Created at: May 3, 2026, 4:31 p.m.