Triple
T20381663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dainty June |
E497846
|
entity |
| Predicate | performsInSetting |
P115811
|
FINISHED |
| Object | vaudeville circuit |
—
|
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: vaudeville circuit | Statement: [Dainty June, performsInSetting, vaudeville circuit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performsInSetting Context triple: [Dainty June, performsInSetting, vaudeville circuit]
-
A.
worksInSetting
chosen
Indicates that an entity performs its activities or functions within a specified environment, context, or setting.
-
B.
performsAt
Indicates that an entity carries out or presents a performance at a specific location, venue, or event.
-
C.
performsAs
Indicates that one entity takes on, enacts, or fulfills the role, function, or character of another entity.
-
D.
indicatedSetting
Indicates that one entity specifies, denotes, or points out a particular setting or configuration associated with another entity.
-
E.
basedOnSetting
Indicates that one entity is derived from, influenced by, or constructed using the setting or contextual environment defined by another entity.
- 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_69e0b4a5b7908190a972e4e7e698ae94 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e678b0ee708190bdbe4aab28a61525 |
completed | April 20, 2026, 7:04 p.m. |
| PD | Predicate disambiguation | batch_69e57648be3c81908256838228cabf5c |
completed | April 20, 2026, 12:41 a.m. |
Created at: April 16, 2026, 11:27 a.m.