Triple
T9632826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RPL programming language |
E232847
|
entity |
| Predicate | supportsNotation |
P57346
|
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: [RPL programming language, supportsNotation, reverse Polish notation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsNotation Context triple: [RPL programming language, supportsNotation, reverse Polish notation]
-
A.
hasAlternativeNotation
chosen
Indicates that an entity can be represented or written in a different, equivalent form or notation.
-
B.
hasObjectNotation
Indicates that an entity is represented or expressed using a specific object-based notation or symbolic format.
-
C.
supportsAt
Indicates that one entity provides assistance, endorsement, or backing to another entity in a specific context, location, or point in time.
-
D.
supportsType
Indicates that one entity is capable of handling, accepting, or being compatible with a specified type.
-
E.
supportsFeature
Indicates that one entity provides, enables, or is compatible with a particular feature or capability of another.
- 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_69ca848940cc8190b97cec654cb3bb4a |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9b2783b48190a9929dc3e3cd2956 |
completed | April 1, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69ccd5acfa5c8190aaba3cf548723604 |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:11 p.m.