Triple
T550395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Game of Thrones Main Title |
E11824
|
entity |
| Predicate | hasArrangement |
P15612
|
FINISHED |
| Object | orchestral arrangement |
—
|
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: orchestral arrangement | Statement: [Game of Thrones Main Title, hasArrangement, orchestral arrangement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasArrangement Context triple: [Game of Thrones Main Title, hasArrangement, orchestral arrangement]
-
A.
hasOrder
Indicates that one entity possesses, is associated with, or is characterized by a specific order, sequence, or arrangement relative to others.
-
B.
hasAccord
Indicates that there is a formal agreement, harmony, or concord between the related entities.
-
C.
hasPlan
Indicates that an entity possesses or is associated with a specific plan or course of action.
-
D.
availableWith
Indicates that one entity can be obtained, accessed, or used in conjunction with another entity.
-
E.
hasPar
Indicates a relationship where one entity has another entity as its parent.
- F. None of above. chosen
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_69a4932941d08190815efd422f0b4ca7 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a499030cf4819089b9163102255e49 |
completed | March 1, 2026, 7:52 p.m. |
| PD | Predicate disambiguation | batch_69a494bae210819093c2e0d33a8ca51a |
completed | March 1, 2026, 7:34 p.m. |
| PDg | Predicate description generation | batch_69a49858abd48190bd4b002a93e4a908 |
completed | March 1, 2026, 7:49 p.m. |
Created at: March 1, 2026, 7:32 p.m.