Triple
T4195432
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Willo Perron |
E89140
|
entity |
| Predicate | hasDesigned |
P54291
|
FINISHED |
| Object | tour stage productions |
—
|
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: tour stage productions | Statement: [Willo Perron, hasDesigned, tour stage productions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDesigned Context triple: [Willo Perron, hasDesigned, tour stage productions]
-
A.
hasDesign
Indicates that one entity possesses, embodies, or is characterized by a particular design associated with another entity.
-
B.
hasPartInHisDesign
Indicates that one entity is included as a component or element within the design or plan created by another entity.
-
C.
isDesignedAs
Indicates that something has been intentionally created or configured to serve as or function in the role of something else.
-
D.
designedWith
Indicates that one entity was created, planned, or developed using another entity as a tool, method, or guiding basis in its design process.
-
E.
hasDesignAuthority
Indicates that one entity holds the recognized power or responsibility to make or approve design decisions affecting 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_69aed9569a4481908b6c1fcec2a11e21 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af035e87148190a0f0bf48b813ffaa |
completed | March 9, 2026, 5:29 p.m. |
| PD | Predicate disambiguation | batch_69af01959c4881909eb1adcb3bdadbe6 |
completed | March 9, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69af02e4e2308190b527e3b78eb8fa71 |
completed | March 9, 2026, 5:27 p.m. |
Created at: March 9, 2026, 3:46 p.m.