Triple
T31170636
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tinker Tailor Soldier Sailor Rich Man Poor Man Beggar Man Thief |
E794593
|
entity |
| Predicate | hasIntricateArrangement |
P15612
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Tinker Tailor Soldier Sailor Rich Man Poor Man Beggar Man Thief, hasIntricateArrangement, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIntricateArrangement Context triple: [Tinker Tailor Soldier Sailor Rich Man Poor Man Beggar Man Thief, hasIntricateArrangement, true]
-
A.
isArrangementOf
Indicates that one entity is a specific ordering or configuration of the components or elements of another entity.
-
B.
hasArrangement
chosen
Indicates that one entity possesses, follows, or is organized according to a particular configuration, setup, or ordering defined by another entity.
-
C.
containsArrangementsStyle
Indicates that one entity includes or features musical arrangements characterized by a particular style or stylistic approach.
-
D.
arrangementFeatures
Indicates that one entity specifies or characterizes the structural or compositional features of an arrangement involving another entity.
-
E.
hasArrangementFor
Indicates that one entity has an established plan, setup, or provision in place to accommodate, support, or serve another entity or purpose.
- 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_69f224d5b9708190b6ca79ad2fd3a28a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69ff27b125948190aced0fe0189fd39a |
completed | May 9, 2026, 12:25 p.m. |
| PD | Predicate disambiguation | batch_69ff26c30a0481909ef6a54ded851e42 |
completed | May 9, 2026, 12:21 p.m. |
Created at: April 29, 2026, 9:07 p.m.