Triple
T21922244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ArrayComm |
E541347
|
entity |
| Predicate | hasTechnologyCategory |
P133726
|
FINISHED |
| Object | smart antenna systems |
—
|
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: smart antenna systems | Statement: [ArrayComm, hasTechnologyCategory, smart antenna systems]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTechnologyCategory Context triple: [ArrayComm, hasTechnologyCategory, smart antenna systems]
-
A.
hasTechnologyDomain
Indicates that an entity is associated with, operates within, or is relevant to a particular field or domain of technology.
-
B.
hasTechnologyTheme
Indicates that something is associated with, centers on, or prominently features technology as a primary theme or subject.
-
C.
hasTechnologySystem
chosen
Indicates that one entity possesses, utilizes, or is supported by a particular technology system.
-
D.
hasTechnologyBrand
Indicates that one entity possesses, is associated with, or uses a particular technology-related brand.
-
E.
inUniverseTechnologyOf
Indicates that a technology exists within, and is part of, the fictional universe or setting associated with a given 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_69e0c47d74488190a15119108794a307 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f1233c29008190b84ae551b14eb2db |
completed | April 28, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69e6f5efc208819091ed2cf6841fa600 |
completed | April 21, 2026, 3:58 a.m. |
Created at: April 16, 2026, 7:45 p.m.