Triple
T14529280
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mademoiselle Reisz |
E340859
|
entity |
| Predicate | testsInEdna |
P114625
|
FINISHED |
| Object | strength of artistic commitment |
—
|
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: strength of artistic commitment | Statement: [Mademoiselle Reisz, testsInEdna, strength of artistic commitment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: testsInEdna Context triple: [Mademoiselle Reisz, testsInEdna, strength of artistic commitment]
-
A.
testsIn
Indicates that one entity conducts or performs tests within, on, or using another entity.
-
B.
tests
Indicates that one entity examines, evaluates, or checks another entity or condition to determine its properties, performance, or correctness.
-
C.
testedInCase
Indicates that something (such as a method, component, or behavior) is exercised or verified within a particular test case.
-
D.
testedFor
Indicates that an entity has been examined or analyzed to determine the presence, absence, or level of another specified entity or condition.
-
E.
appliedTest
Indicates that a test has been administered or carried out on a particular subject or object.
- 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_69d822dac79c8190a84a073f3cbaced5 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dea051bc608190ad4d516c5e7bca43 |
completed | April 14, 2026, 8:15 p.m. |
| PD | Predicate disambiguation | batch_69de5c518fc08190a6ce4d8be05c4c5d |
completed | April 14, 2026, 3:25 p.m. |
| PDg | Predicate description generation | batch_69de5fb5ac548190932f238e37271741 |
completed | April 14, 2026, 3:39 p.m. |
Created at: April 10, 2026, 1:22 a.m.