Triple
T25938135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NRQZ |
E653616
|
entity |
| Predicate | restrictedTechnology |
P159846
|
FINISHED |
| Object | microwave transmitters |
—
|
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: microwave transmitters | Statement: [NRQZ, restrictedTechnology, microwave transmitters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: restrictedTechnology Context triple: [NRQZ, restrictedTechnology, microwave transmitters]
-
A.
restrictedFromUseFor
Indicates that something is prohibited or limited from being used for a specified purpose, context, or application.
-
B.
restrictedRight
Indicates that an entity’s ability to exercise a particular right is limited, constrained, or subject to specific conditions or prohibitions.
-
C.
allowedTechnique
Indicates that a particular technique or method is permitted or acceptable to use in a given context or under specified rules.
-
D.
productionRestrictedTo
Indicates that the production or manufacture of something is limited or confined to a specified location, entity, or set of conditions.
-
E.
distributionRestricted
Indicates that the distribution or sharing of something is limited or controlled by specific restrictions or conditions.
- 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_69e7ab3fd2f881908837305e4ba98011 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6045b07b08190a58fd7e0acda574c |
completed | May 2, 2026, 2:04 p.m. |
| PD | Predicate disambiguation | batch_69f5afec3e94819080d9ba86cf8c866e |
completed | May 2, 2026, 8:03 a.m. |
| PDg | Predicate description generation | batch_69f5f6b32a8881909baa0db57b80d56a |
completed | May 2, 2026, 1:05 p.m. |
Created at: April 22, 2026, 8:40 a.m.