Triple
T31729133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WWV 111 |
E809806
|
entity |
| Predicate | subjectWorkStructure |
P188105
|
FINISHED |
| Object | three acts |
—
|
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: three acts | Statement: [WWV 111, subjectWorkStructure, three acts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subjectWorkStructure Context triple: [WWV 111, subjectWorkStructure, three acts]
-
A.
workStructure
Indicates how work is organized, arranged, or structured within or between entities.
-
B.
sourceWorkStructure
Indicates that one work serves as the structural or organizational basis for another work.
-
C.
relatedWorkStructure
Indicates that one work has a structural or organizational relationship to another work, such as being a part, version, adaptation, or otherwise structurally derived or connected.
-
D.
refersToWorkStructure
Indicates that one entity references or is associated with a particular work-related organizational structure or framework.
-
E.
subjectStructure
Indicates that one entity serves as the structural form, framework, or configuration in which the other entity is organized or embodied.
- 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_69f348e009c8819095d77df52c645b9c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fba2877b248190a974eb092243c0c4 |
completed | May 6, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69fb8d06a1b48190a937aa410d159dfa |
completed | May 6, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69fba28684208190921694f23e350c3b |
completed | May 6, 2026, 8:20 p.m. |
Created at: April 30, 2026, 11:21 p.m.