Triple
T1935109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wi‑Fi |
E41426
|
entity |
| Predicate | usesTopology |
P33685
|
FINISHED |
| Object | infrastructure mode |
—
|
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: infrastructure mode | Statement: [Wi‑Fi, usesTopology, infrastructure mode]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesTopology Context triple: [Wi‑Fi, usesTopology, infrastructure mode]
-
A.
hasTopology
Indicates that one entity possesses, exhibits, or is characterized by a particular structural or spatial configuration defined by the other entity.
-
B.
topology
Indicates the structural or spatial arrangement and connectivity pattern among components within a system.
-
C.
topographyBasedOn
Indicates that the topographical characteristics of one entity are derived from, determined by, or modeled using the topography of another entity.
-
D.
usesInfrastructure
Indicates that one entity makes use of, depends on, or operates through the infrastructure provided or managed by another entity.
-
E.
allowsSpatialCurvature
Indicates that one entity permits or enables the presence or variation of spatial curvature in relation to another entity or context.
- 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_69a88649b24c819080047f26b6db2ded |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb29c7be08190986df157bf5d7c9e |
completed | March 7, 2026, 5:07 a.m. |
| PD | Predicate disambiguation | batch_69abaff07cf88190b4883c5f17f90abd |
completed | March 7, 2026, 4:56 a.m. |
| PDg | Predicate description generation | batch_69abb25ef0ec8190b907963e9db0fe04 |
completed | March 7, 2026, 5:06 a.m. |
Created at: March 4, 2026, 7:35 p.m.