Triple
T24360425
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Au Revoir Parapluie |
E614039
|
entity |
| Predicate | usesPerformanceDiscipline |
P98353
|
FINISHED |
| Object | acrobatics |
—
|
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: acrobatics | Statement: [Au Revoir Parapluie, usesPerformanceDiscipline, acrobatics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesPerformanceDiscipline Context triple: [Au Revoir Parapluie, usesPerformanceDiscipline, acrobatics]
-
A.
usedForDiscipline
Indicates that one entity is employed as a means or tool to impose discipline or enforce behavioral control on another entity.
-
B.
performanceUse
Indicates that something is used, employed, or utilized in the course of performing an action, task, or function.
-
C.
usesToolFromDiscipline
chosen
Indicates that an entity employs a tool, method, or technique that originates from or is characteristic of a particular discipline or field.
-
D.
performanceWith
Indicates a relationship where two or more entities participate together in the same performance or staged presentation.
-
E.
supportsDiscipline
Indicates that one entity provides assistance, resources, or endorsement that helps sustain or advance a particular discipline.
- 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_69e2d7dfe7f08190b7a1f3a36483ab05 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f29383ccb88190a4752fe7ccd93fd5 |
completed | April 29, 2026, 11:25 p.m. |
| PD | Predicate disambiguation | batch_69f287bb1b2c81909c2e7fcc392ad143 |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2 a.m.