Triple
T3744793
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | shunting-yard algorithm |
E79783
|
entity |
| Predicate | processingOrder |
P51068
|
FINISHED |
| Object | left-to-right scan of input tokens |
—
|
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: left-to-right scan of input tokens | Statement: [shunting-yard algorithm, processingOrder, left-to-right scan of input tokens]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: processingOrder Context triple: [shunting-yard algorithm, processingOrder, left-to-right scan of input tokens]
-
A.
processingUse
Indicates that one entity uses or applies another entity as part of a processing or transformation activity.
-
B.
subsequentOrder
Indicates that one order occurs after or follows another order in sequence.
-
C.
order
Indicates that one entity requests, arranges, or directs that another entity provide a good, service, or action, typically in a specified sequence or priority.
-
D.
entersOrderThrough
Indicates that one party places or submits an order by means of, or via the involvement of, another party or system.
-
E.
partOfProcess
Indicates that one event, step, or action occurs as a component or stage within a larger overall process.
- 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_69ad8b115610819095b02007da5ca3cb |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcb58c9048190a055d1f4a7e6b699 |
completed | March 8, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69adc04adebc819088d7f36d0ac343a6 |
completed | March 8, 2026, 6:30 p.m. |
| PDg | Predicate description generation | batch_69adc1560c248190b07438d766880990 |
completed | March 8, 2026, 6:35 p.m. |
Created at: March 8, 2026, 3:34 p.m.