Triple
T30879706
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haydn symphonies |
E786577
|
entity |
| Predicate | primaryCompositionLocation |
P7607
|
FINISHED |
| Object | Esterháza |
E1811957
|
NE 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: Esterháza | Statement: [Haydn symphonies, primaryCompositionLocation, Esterháza]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryCompositionLocation Context triple: [Haydn symphonies, primaryCompositionLocation, Esterháza]
-
A.
primaryLocationIn
Indicates that an entity’s main or most significant location is within or at the referenced place.
-
B.
placeOfComposition
chosen
Indicates the location where a work was created or composed.
-
C.
primaryPostingLocation
Indicates the main or default location where an entity (such as a message, job, or content item) is originally posted or primarily published.
-
D.
cityOfComposition
Indicates the city where a work was created or composed.
-
E.
possiblePlaceOfComposition
Indicates that a location is a plausible or hypothesized place where a work was composed.
- F. None of above.
Provenance (4 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_69f224bae17c8190bb3a6a28e3d019df |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a03446ec72881909c5ff25a48baadb3 |
completed | May 12, 2026, 3:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a292af72f508190b11b5d4d193983c4 |
completed | June 10, 2026, 9:14 a.m. |
| PD | Predicate disambiguation | batch_6a03439b393c819084aa9b7ed0d5b6b0 |
completed | May 12, 2026, 3:13 p.m. |
Created at: April 29, 2026, 8:48 p.m.