Triple
T23822977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Erismena |
E589285
|
entity |
| Predicate | hasNumberType |
P153762
|
FINISHED |
| Object | recitative |
—
|
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: recitative | Statement: [Erismena, hasNumberType, recitative]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNumberType Context triple: [Erismena, hasNumberType, recitative]
-
A.
hasNumberCategory
Indicates that an entity is associated with a specific numerical classification or type.
-
B.
hasNumberInStructure
Indicates that an entity’s structure includes or contains a specific numerical value or component.
-
C.
numericType
Indicates that one entity specifies or constrains the kind or category of numeric value associated with another entity.
-
D.
hasNumberOfTypes
Indicates that an entity is associated with a specific count of distinct types or categories it possesses or includes.
-
E.
hasNumericalValue
Indicates that an entity is associated with a specific numeric quantity or measurement.
- 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_69e25d18619081909c7fb89d8926f14a |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c7afff6c819096a0af7e008ea8d4 |
completed | April 29, 2026, 8:56 a.m. |
| PD | Predicate disambiguation | batch_69f156036ad48190bc2ffdaf39218bcb |
completed | April 29, 2026, 12:51 a.m. |
| PDg | Predicate description generation | batch_69f158b0e320819090b947ee7eb14116 |
completed | April 29, 2026, 1:02 a.m. |
Created at: April 17, 2026, 7:59 p.m.