Triple
T35362977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ENY |
E1021543
|
entity |
| Predicate | relatedCallsign |
—
|
GENERATED |
| Object | ENVOY |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedCallsign Context triple: [ENY, relatedCallsign, ENVOY]
-
A.
relatedCallsignUsage
Indicates that one callsign is used in connection with, or as a variant of, another callsign in operational or identification contexts.
-
B.
inspiredCallsignOf
Indicates that one entity’s callsign was created based on, influenced by, or derived from another entity.
-
C.
callsignSharedWithParent
Indicates that an entity uses the same callsign as its parent entity, rather than having a distinct callsign of its own.
-
D.
callsign
Indicates that an entity is assigned or uses a specific radio or identification callsign as its designated identifier in communication contexts.
-
E.
callsignSeries
Indicates that one entity is a member or installment within a series or sequence that shares the same callsign.
- F. None of above. chosen
Provenance (1 batch)
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_69f76def44c881908a20e8008572eb44 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:03 p.m.