Triple
T30311417
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nicklausse |
E770932
|
entity |
| Predicate | hasAriaOrNumber |
P190055
|
FINISHED |
| Object | “Vois sous l’archet frémissant” |
—
|
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: “Vois sous l’archet frémissant” | Statement: [Nicklausse, hasAriaOrNumber, “Vois sous l’archet frémissant”]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAriaOrNumber Context triple: [Nicklausse, hasAriaOrNumber, “Vois sous l’archet frémissant”]
-
A.
hasNumberInStructure
Indicates that an entity’s structure includes or contains a specific numerical value or component.
-
B.
hasNumericalValue
Indicates that an entity is associated with a specific numeric quantity or measurement.
-
C.
hasNumberingRole
Indicates that an entity holds a specific role or responsibility related to assigning, managing, or using numbers within a given context.
-
D.
hasNumberType
Indicates that an entity is associated with a specific category or type of number (such as integer, float, or identifier format).
-
E.
containsNumber
Indicates that one entity includes or has at least one numeric value or digit within it.
- 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_69f22488f224819081b0f3ec41ab975c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fcab6e888881908ca9e18660928a40 |
completed | May 7, 2026, 3:10 p.m. |
| PD | Predicate disambiguation | batch_69fc4562a5b88190bad48f083a6dcdfa |
completed | May 7, 2026, 7:55 a.m. |
| PDg | Predicate description generation | batch_69fcab6d41a88190a3576b4b088dcabd |
completed | May 7, 2026, 3:10 p.m. |
Created at: April 29, 2026, 7:50 p.m.