Triple
T23821955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prohibition Party |
E589259
|
entity |
| Predicate | continuousOperation |
P147910
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Prohibition Party, continuousOperation, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: continuousOperation Context triple: [Prohibition Party, continuousOperation, yes]
-
A.
continuousPlay
chosen
Indicates that an activity or process proceeds without interruption or breaks over a period of time.
-
B.
inOperationDuring
Indicates that an entity is actively functioning or in use throughout a specified time period or event.
-
C.
continuedFreightOperationsUntil
Indicates that an entity maintained its freight transportation activities up to and including a specified point in time.
-
D.
operatorDuringOperation
Indicates that an operator is the one performing or responsible for an operation during its execution.
-
E.
inOperation
Indicates that an entity (such as a system, device, or facility) is currently active, functioning, and performing its intended operation.
- 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_69e25d18619081909c7fb89d8926f14a |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c7afff6c819096a0af7e008ea8d4 |
completed | April 29, 2026, 8:56 a.m. |
| PD | Predicate disambiguation | batch_69f156036ad48190bc2ffdaf39218bcb |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:59 p.m.