Triple
T31819647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polish notation |
E812224
|
entity |
| Predicate | relatedNotation |
P207527
|
FINISHED |
| Object | reverse Polish notation |
—
|
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: reverse Polish notation | Statement: [Polish notation, relatedNotation, reverse Polish notation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedNotation Context triple: [Polish notation, relatedNotation, reverse Polish notation]
-
A.
relatedPass
Indicates that one pass is associated with or connected to another pass in some relevant way.
-
B.
relatedType
Indicates that one entity is connected to another through a specified type or category of relationship.
-
C.
relatedClassification
Indicates a relationship where one classification is associated with, linked to, or otherwise contextually connected to another classification.
-
D.
relatedPattern
Indicates that one entity is associated with or connected to another through a shared or corresponding pattern.
-
E.
relatedMap
Indicates that one entity is associated with another through a mapping or correspondence relationship, typically linking related items or concepts.
- 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_69f348e97fa48190aa06286962af6dee |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e7aa0c8190bdc9ee4d54fc821b |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7ee0388190a29faeb5cdb0950a |
completed | May 12, 2026, 7:16 p.m. |
Created at: April 30, 2026, 11:45 p.m.