Triple
T35735711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sainte-Colombe |
E1032879
|
entity |
| Predicate | workList |
P169337
|
FINISHED |
| Object | over 60 Concerts à deux violes esgales |
—
|
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: over 60 Concerts à deux violes esgales | Statement: [Sainte-Colombe, workList, over 60 Concerts à deux violes esgales]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workList Context triple: [Sainte-Colombe, workList, over 60 Concerts à deux violes esgales]
-
A.
workListIn
chosen
Indicates that an item is included within or assigned to a particular work list.
-
B.
worksFrom
Indicates that an entity performs its work or duties starting from or based at a specified location or source.
-
C.
workBy
Indicates that a work (such as a creation, product, or result) is produced, authored, or created by a particular agent or entity.
-
D.
workWith
Indicates that one entity collaborates or engages in work-related activities together with another entity.
-
E.
workOn
Indicates that an agent is actively engaged in performing tasks or making progress on a particular project, object, or assignment.
- 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_69f76e10e59081908d81ad9ce22f40b6 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a34f8ee08190a040304635539a8f |
completed | May 3, 2026, 7:34 p.m. |
| PD | Predicate disambiguation | batch_69f7a06f125c8190843af194f042a465 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:05 p.m.