Triple
T13313533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | French theatre |
E317131
|
entity |
| Predicate | hasPerformanceForm |
P79011
|
FINISHED |
| Object | spoken drama |
—
|
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: spoken drama | Statement: [French theatre, hasPerformanceForm, spoken drama]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPerformanceForm Context triple: [French theatre, hasPerformanceForm, spoken drama]
-
A.
hasPerformanceElement
chosen
Indicates that one entity includes, contains, or is associated with a specific performance-related component or element.
-
B.
hasPerformanceConvention
Indicates that there is an agreed-upon set of rules, norms, or standards governing how a particular performance or activity should be carried out.
-
C.
hasPerformanceLocation
Indicates that an event, performance, or show takes place at a specified location or venue.
-
D.
hasPerformancePackage
Indicates that an entity is equipped with or associated with a specific performance-enhancing package or upgrade.
-
E.
hasSignaturePerformanceBy
Indicates that something features a standout or defining performance delivered by a particular performer.
- 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_69d806b40ab4819094adf6c374f4811a |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f6babd88190a5d529df9584b9a4 |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:29 p.m.