Triple
T26738669
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clopin |
E674183
|
entity |
| Predicate | performsNumberType |
P142479
|
FINISHED |
| Object | ensemble songs |
—
|
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: ensemble songs | Statement: [Clopin, performsNumberType, ensemble songs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performsNumberType Context triple: [Clopin, performsNumberType, ensemble songs]
-
A.
performsNumber
Indicates that an entity carries out or executes a specific numbered item, such as a task, role, or performance identified by that number.
-
B.
performsInNumber
chosen
Indicates that an entity takes part as a performer in a specific musical, theatrical, or similar numbered production or piece.
-
C.
hasNumberType
Indicates that an entity is associated with a specific category or type of number (such as integer, float, or identifier format).
-
D.
numericType
Indicates that one entity specifies or constrains the kind or category of numeric value associated with another entity.
-
E.
operatesOnCallNumberType
Indicates that an entity performs operations specifically on items identified by a particular call number type.
- 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_69eecda57ab481909424e98f2835e7d8 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f6d0d46aec819091edf97324d793ac |
completed | May 3, 2026, 4:36 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe2183481908ae4e85a59c66f69 |
completed | May 3, 2026, 4:32 a.m. |
Created at: April 27, 2026, 3:48 a.m.