Triple
T5213289
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stagecrafters Baldwin Theatre |
E117684
|
entity |
| Predicate | staffingModel |
P11922
|
FINISHED |
| Object | volunteer-based |
—
|
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: volunteer-based | Statement: [Stagecrafters Baldwin Theatre, staffingModel, volunteer-based]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: staffingModel Context triple: [Stagecrafters Baldwin Theatre, staffingModel, volunteer-based]
-
A.
hasWorkforceType
chosen
Indicates the type or category of workforce associated with an entity (such as permanent, temporary, contract, or part-time).
-
B.
staffIncluded
Indicates that staff members are included or provided as part of the associated entity, service, or arrangement.
-
C.
workModel
Indicates that one entity serves as, or is based on, a particular model used for work, operation, or functional behavior.
-
D.
compensationModel
Indicates the type or structure of payment or rewards provided in exchange for work, services, or performance.
-
E.
associatedWithWorkforce
Indicates a relationship in which an entity is connected or related to a particular workforce, such as its members, activities, or management.
- 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_69bd4464ba3c8190bc16b2ebbe42ddb0 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7a911d40819086621537274dc0f0 |
completed | March 20, 2026, 4:49 p.m. |
| PD | Predicate disambiguation | batch_69bd77bb4e8c819094b5ac7cf61512f9 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:47 p.m.