Triple
T37331488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stage Manager (Our Town) |
E926762
|
entity |
| Predicate | describesSettingVerbally |
P25484
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Stage Manager (Our Town), describesSettingVerbally, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: describesSettingVerbally Context triple: [Stage Manager (Our Town), describesSettingVerbally, true]
-
A.
settingDescription
chosen
Indicates the descriptive details or characteristics that define the context or environment in which something occurs.
-
B.
indicatedSetting
Indicates that one entity specifies, denotes, or points out a particular setting or configuration associated with another entity.
-
C.
outputDescription
Indicates that an entity produces or generates a particular description as its output.
-
D.
coversSetting
Indicates that one entity includes or addresses a particular setting or context within its scope.
-
E.
speakerConfiguration
Indicates how speakers are arranged or assigned within an audio or communication setup.
- 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_69f76eb386d88190a8d511aa11540dfc |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fdbc5ef46c8190bbcfb9798f4615b7 |
completed | May 8, 2026, 10:35 a.m. |
| PD | Predicate disambiguation | batch_69fdbb270338819082ce3f73903e884f |
completed | May 8, 2026, 10:29 a.m. |
Created at: May 3, 2026, 4:16 p.m.