Triple
T20847028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ANQP |
E513256
|
entity |
| Predicate | queryDirection |
P142074
|
FINISHED |
| Object | from Wi‑Fi client to access point |
—
|
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: from Wi‑Fi client to access point | Statement: [ANQP, queryDirection, from Wi‑Fi client to access point]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: queryDirection Context triple: [ANQP, queryDirection, from Wi‑Fi client to access point]
-
A.
directionType
Indicates the specific kind or category of direction associated with a movement, orientation, or relation between entities.
-
B.
directionBy
Indicates that one entity provides directional guidance, orientation, or navigational reference for another entity.
-
C.
containsDirectionOf
Indicates that one entity includes or encompasses the directional orientation or path associated with another entity.
-
D.
rangeDirection
Indicates the directional orientation or bearing associated with a specified range between entities.
-
E.
isDirection
Indicates that one entity specifies or represents the orientation or course along which another entity moves, points, or is aligned.
- 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_69e0b4f4898081908209e58edb8f9c45 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c34ffb588190881953a0480b29a8 |
completed | April 21, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a593f481908beb457c29f1ce73 |
completed | April 20, 2026, 6:37 a.m. |
| PDg | Predicate description generation | batch_69e5d53c4d6881909b4d0a716fa5ed4a |
completed | April 20, 2026, 7:26 a.m. |
Created at: April 16, 2026, 12:43 p.m.