Triple
T34498883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barbara Strozzi |
E885692
|
entity |
| Predicate | hasApproximateWorkCount |
P34532
|
FINISHED |
| Object | over 100 vocal works |
—
|
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 100 vocal works | Statement: [Barbara Strozzi, hasApproximateWorkCount, over 100 vocal works]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproximateWorkCount Context triple: [Barbara Strozzi, hasApproximateWorkCount, over 100 vocal works]
-
A.
hasWorkCount
chosen
Indicates the number of works (such as items, creations, or outputs) associated with a given entity.
-
B.
hasApproximateNumberOfRuns
Indicates that an entity is associated with a number of runs that is approximate rather than exact.
-
C.
hasNumberOfTasks
Indicates that an entity is associated with a specific count of tasks.
-
D.
hasApproximateNumberOfResponsa
Indicates that an entity is associated with a rough or estimated count of responsa, rather than an exact number.
-
E.
hasDistributedWorkOf
Indicates that an entity has assigned, allocated, or spread a particular work, task, or workload to another entity for execution or handling.
- 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_69f349cafcec8190997b45b3fdc16c27 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd68abf52881909c5a390c362b7c59 |
completed | May 8, 2026, 4:38 a.m. |
| PD | Predicate disambiguation | batch_69fd6812d0c88190930d8fa2d4b92490 |
completed | May 8, 2026, 4:35 a.m. |
Created at: May 1, 2026, 2:01 a.m.