Triple
T27281343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ‘Servais’ Stradivarius cello (1701) |
E688339
|
entity |
| Predicate | stringFamily |
P162302
|
FINISHED |
| Object | cello |
—
|
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: cello | Statement: [‘Servais’ Stradivarius cello (1701), stringFamily, cello]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stringFamily Context triple: [‘Servais’ Stradivarius cello (1701), stringFamily, cello]
-
A.
textualFamily
Indicates that two or more texts are related through a shared origin, tradition, or lineage, forming a recognizable textual group or family.
-
B.
syntaxFamily
Indicates that two linguistic elements share a common syntactic type, pattern, or structural classification within a grammar system.
-
C.
typeFamily
Indicates that one entity is classified as a family-related type or belongs to a family category in relation to another entity.
-
D.
featuresFamilyName
Indicates that an entity is associated with or displays a particular family name.
-
E.
styleFamily
Indicates that one style is grouped within the same stylistic family or category as another style.
- 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_69ef355998e08190bdff849e8f33adce |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f6272d55e48190bb2eb6bd4c120daf |
completed | May 2, 2026, 4:32 p.m. |
| PD | Predicate disambiguation | batch_69f620e38aec8190bb184edcdbd6da64 |
completed | May 2, 2026, 4:05 p.m. |
| PDg | Predicate description generation | batch_69f622a8fe7c819096e8a43db263a423 |
completed | May 2, 2026, 4:13 p.m. |
Created at: April 27, 2026, 11:07 a.m.