Triple
T32902961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WWV 49 |
E841659
|
entity |
| Predicate | appliesToNumberOfActs |
P12050
|
FINISHED |
| Object | five-act work |
—
|
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: five-act work | Statement: [WWV 49, appliesToNumberOfActs, five-act work]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesToNumberOfActs Context triple: [WWV 49, appliesToNumberOfActs, five-act work]
-
A.
numberOfActs
chosen
Indicates the total count of discrete acts or actions associated with a given entity or event.
-
B.
hasNumberInActa
Indicates that an entity is associated with a specific identifying number recorded in an official acta (formal record or document).
-
C.
hasActs
Indicates that an entity is associated with one or more actions, performances, or deeds it carries out or is responsible for.
-
D.
isNumberInAct
Indicates that a specific number appears within, or is associated with, a particular act (such as a legal act, play act, or similar structured unit).
-
E.
passesActsCalled
Indicates that one entity (typically a legislative body or authority) formally approves and enacts acts or laws that are referred to by a specific name.
- 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_69f34946a5208190bbd79f0fec4323bd |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fee691952c8190822da83e46311d1d |
completed | May 9, 2026, 7:47 a.m. |
| PD | Predicate disambiguation | batch_69fee62f285c8190a625562a9b80526e |
completed | May 9, 2026, 7:45 a.m. |
Created at: May 1, 2026, 1:19 a.m.