Triple
T16907638
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WEB |
E424602
|
entity |
| Predicate | sectionOrdering |
P58213
|
FINISHED |
| Object | logical order for human readers |
—
|
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: logical order for human readers | Statement: [WEB, sectionOrdering, logical order for human readers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sectionOrdering Context triple: [WEB, sectionOrdering, logical order for human readers]
-
A.
displayOrder
chosen
Indicates the sequence or position in which items should be presented or shown relative to one another.
-
B.
selectionOrderAdjustment
Indicates a modification to the original order in which items or options were selected, such as reordering or adjusting their selection sequence.
-
C.
fieldOrder
Indicates the sequence or arrangement in which fields are ordered relative to one another.
-
D.
columnOrder
Indicates the relative sequencing or arrangement of columns within a structured layout or dataset.
-
E.
confersOrder
Indicates that one entity formally bestows or grants an order, rank, or honorific distinction upon another entity.
- 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_69d889da3e8c8190a2b118f383f0beac |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e3ca39f9b08190b15106c6caf895ec |
completed | April 18, 2026, 6:15 p.m. |
| PD | Predicate disambiguation | batch_69e32b9489408190bcb2ede567ff5bf9 |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:30 a.m.