Triple
T29026884
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Symphony No. 3 |
E737615
|
entity |
| Predicate | isLargeScaleWork |
P87672
|
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: [Symphony No. 3, isLargeScaleWork, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLargeScaleWork Context triple: [Symphony No. 3, isLargeScaleWork, true]
-
A.
hasLargeScale
Indicates that an entity operates, exists, or is implemented at a large or extensive scale relative to typical or baseline cases.
-
B.
workScale
chosen
Indicates the relative magnitude, intensity, or scope at which a given work activity, project, or operation is carried out.
-
C.
isSmallScale
Indicates that the related activity, operation, or entity occurs on a limited or minor scale, involving relatively small size, scope, or capacity.
-
D.
hasSignificantWorkType
Indicates that an entity is associated with a primary or notably important type or category of work.
-
E.
hasMajorWork
Indicates that an entity (typically a person, creator, or organization) is associated with a significant or principal work they produced or are best known for.
- 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_69f077ef00fc81909325f084ad37c035 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f6600b2ea0819080d54e0400bd3364 |
completed | May 2, 2026, 8:35 p.m. |
| PD | Predicate disambiguation | batch_69f65c2376a08190be5215171e908e69 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 9:53 a.m.