Triple
T10437080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | E-band systems |
E246071
|
entity |
| Predicate | typicalLinkType |
P93585
|
FINISHED |
| Object | line-of-sight link |
—
|
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: line-of-sight link | Statement: [E-band systems, typicalLinkType, line-of-sight link]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalLinkType Context triple: [E-band systems, typicalLinkType, line-of-sight link]
-
A.
linkType
Indicates the specific kind or category of relationship that connects two linked entities.
-
B.
typicalEntryType
Indicates the usual or standard category or kind of entry associated with something.
-
C.
typicalCoreType
Indicates that something is a standard or characteristic core type within a given classification or system.
-
D.
relatedType
Indicates that one entity is connected to another through a specified type or category of relationship.
-
E.
typicalSegmentType
Indicates that something is classified as belonging to a usual or characteristic type of segment within a broader structure or sequence.
- 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_69d381bf3dc08190bf35a2643e4e8f22 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4ea853c308190be95ae8dffe67ac1 |
completed | April 7, 2026, 11:29 a.m. |
| PD | Predicate disambiguation | batch_69d4dfbc546881908f312c66ee195f79 |
completed | April 7, 2026, 10:43 a.m. |
| PDg | Predicate description generation | batch_69d4e91de3088190ae89cbb12fb29db8 |
completed | April 7, 2026, 11:23 a.m. |
Created at: April 6, 2026, 12:14 p.m.