Triple
T37924037
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Between the Acts |
E946040
|
entity |
| Predicate | hasPageantDirector |
P202291
|
FINISHED |
| Object | Miss La Trobe |
—
|
NE NERFINISHED |
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: Miss La Trobe | Statement: [Between the Acts, hasPageantDirector, Miss La Trobe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPageantDirector Context triple: [Between the Acts, hasPageantDirector, Miss La Trobe]
-
A.
hasArtisticDirectorRole
Indicates that an entity holds or fulfills the role of an artistic director in relation to another entity or organization.
-
B.
hasPlaywrightDirector
Indicates a relationship where a play or theatrical work is associated with the person who both wrote it and directed its production.
-
C.
hasArtistDirector
Indicates that one entity serves as the artist director (artistic leader or creative head) of another entity.
-
D.
hasArtDirector
Indicates that an entity has a specific person or organization serving as its art director.
-
E.
hasDirectorStar
Indicates that a person both directed and starred in the same work (e.g., film, show, or production).
- 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_69f76ef3b7248190892fb9706423be7c |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a006ef900148190ba52daf566882a03 |
completed | May 10, 2026, 11:41 a.m. |
| PD | Predicate disambiguation | batch_6a006c76ae748190bfe466d7d17d321e |
completed | May 10, 2026, 11:31 a.m. |
| PDg | Predicate description generation | batch_6a006ef80ce88190b5e3a2b261409d44 |
completed | May 10, 2026, 11:41 a.m. |
Created at: May 3, 2026, 4:20 p.m.