Triple
T37321342
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A Disappearing Number |
E926484
|
entity |
| Predicate | companyStyle |
P195257
|
FINISHED |
| Object | physical theatre |
—
|
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: physical theatre | Statement: [A Disappearing Number, companyStyle, physical theatre]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: companyStyle Context triple: [A Disappearing Number, companyStyle, physical theatre]
-
A.
brandingStyle
Indicates the specific visual and stylistic approach used to represent a brand’s identity.
-
B.
boardingStyle
Indicates the manner or method by which an entity boards or is boarded onto another entity (such as a vehicle, vessel, or platform).
-
C.
teamStyle
Indicates the characteristic way a team typically operates, collaborates, and approaches its work or objectives.
-
D.
officeStyle
Indicates a stylistic or design relationship where one entity’s style is characterized as “office” or suitable for an office environment.
-
E.
styleFor
Indicates a relationship where one entity defines, specifies, or is used as the style or styling configuration applied to another entity.
- 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_69f76eb28af88190b093b32e3fd614ab |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fdb31800508190beec15adb9bbd292 |
completed | May 8, 2026, 9:55 a.m. |
| PD | Predicate disambiguation | batch_69fdb19c381c8190bafb2f565da097f1 |
completed | May 8, 2026, 9:49 a.m. |
| PDg | Predicate description generation | batch_69fdb3172b808190b590d7c5be31ebb7 |
completed | May 8, 2026, 9:55 a.m. |
Created at: May 3, 2026, 4:16 p.m.