Triple
T33879562
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tower Control |
E868446
|
entity |
| Predicate | communicatesOn |
P59911
|
FINISHED |
| Object | tower frequency |
—
|
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: tower frequency | Statement: [Tower Control, communicatesOn, tower frequency]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: communicatesOn Context triple: [Tower Control, communicatesOn, tower frequency]
-
A.
communicatesTo
Indicates that one entity sends or conveys information, messages, or signals to another entity as the intended recipient.
-
B.
communicatesFrom
Indicates that information, messages, or signals are sent or expressed from one entity to another.
-
C.
usedToCommunicate
chosen
Indicates that one entity serves as a medium or tool through which another entity conveys information, messages, or signals.
-
D.
communicatesOnlineWith
Indicates that one entity exchanges messages or information with another entity through online or digital communication channels.
-
E.
designedToCommunicate
Indicates that something has been intentionally created or configured for the purpose of conveying information or messages to others.
- 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_69f34995b81c8190acdb45cea5a10eff |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f71c35327c8190884f1bfe12bd2cd7 |
completed | May 3, 2026, 9:58 a.m. |
| PD | Predicate disambiguation | batch_69f71822d0e88190ac9731c7ae5a4def |
completed | May 3, 2026, 9:40 a.m. |
Created at: May 1, 2026, 1:48 a.m.