Triple
T21568930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Travelling Post Office |
E532233
|
entity |
| Predicate | sortingMethod |
P144284
|
FINISHED |
| Object | manual sorting into pigeon holes |
—
|
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: manual sorting into pigeon holes | Statement: [Travelling Post Office, sortingMethod, manual sorting into pigeon holes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sortingMethod Context triple: [Travelling Post Office, sortingMethod, manual sorting into pigeon holes]
-
A.
comparisonMethod
Indicates the method or criteria used to compare two or more entities or values.
-
B.
sortingObject
Indicates that one entity is performing a sorting operation on another entity or collection.
-
C.
submissionSortingOptions
Indicates how submissions are ordered or prioritized according to specified sorting criteria.
-
D.
sortingOrderSupport
Indicates whether a system or component supports arranging items according to a specified sorting order.
-
E.
comparisonRule
Indicates a rule or criterion that defines how two or more entities are to be compared or evaluated relative to each other.
- 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_69e0c460db088190828c64206a450273 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eee9cad95c8190ab165ced6f242302 |
completed | April 27, 2026, 4:44 a.m. |
| PD | Predicate disambiguation | batch_69e6320c8c2c81908bf031447d66a052 |
completed | April 20, 2026, 2:02 p.m. |
| PDg | Predicate description generation | batch_69e633bf34c481909925d8dc1a633a65 |
completed | April 20, 2026, 2:10 p.m. |
Created at: April 16, 2026, 6:30 p.m.