Triple
T27636704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MatSort |
E696489
|
entity |
| Predicate | defaultDirection |
P154102
|
FINISHED |
| Object | asc |
—
|
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: asc | Statement: [MatSort, defaultDirection, asc]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defaultDirection Context triple: [MatSort, defaultDirection, asc]
-
A.
primaryDirection
Indicates the main or dominant directional orientation associated with an entity or relation.
-
B.
directionType
Indicates the specific kind or category of direction associated with a movement, orientation, or relation between entities.
-
C.
queryDirection
Indicates that one entity requests or specifies the directional orientation or path of another entity or action.
-
D.
definesDirection
Indicates that one entity specifies or establishes the orientation, course, or path along which another entity is directed or proceeds.
-
E.
recommendedDirection
chosen
Indicates the direction that is advised or suggested as the preferred way to move, orient, or proceed in a given context.
- 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_69ef5909f3848190805f35b76833e722 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f643ed0b7481908cf25f3afec0a61d |
completed | May 2, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69f641dc8ff48190ab575d855616580c |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 2:24 p.m.