Triple
T26178722
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PZL.49 Miś |
E654611
|
entity |
| Predicate | projectCancelled |
P7625
|
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: [PZL.49 Miś, projectCancelled, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: projectCancelled Context triple: [PZL.49 Miś, projectCancelled, yes]
-
A.
canceledBy
Indicates that an action, event, or agreement was annulled or called off by a specific entity.
-
B.
constructionProgressAtCancellation
Indicates the level or stage of construction that had been reached at the time the project or contract was cancelled.
-
C.
project
Indicates that an entity plans, organizes, or carries out a structured effort or initiative aimed at achieving a specific goal or outcome.
-
D.
cancellation
chosen
Indicates that a previously planned or scheduled event, action, or agreement is being annulled, terminated, or rendered no longer valid.
-
E.
canceledBefore
Indicates that one event, reservation, or commitment was canceled at a time earlier than another specified event or reference point.
- 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_69ee5b45873c81909499203612d05d07 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f60c6e0768819088a0a5dd82390c09 |
completed | May 2, 2026, 2:38 p.m. |
| PD | Predicate disambiguation | batch_69f5b007ec1c819092e2c3605933f60b |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 26, 2026, 8:39 p.m.