Triple
T35362977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ENY |
E1021543
|
entity |
| Predicate | relatedCallsign |
P206953
|
FINISHED |
| Object | ENVOY |
E1021544
|
NE 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: ENVOY | Statement: [ENY, relatedCallsign, ENVOY]
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 (5 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_69f76def44c881908a20e8008572eb44 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3823dd42d481908486775704558de1 |
completed | June 21, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_6a037a0324d08190ac5b610cc0f6a38c |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82179081908325a59b8539b3a8 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:03 p.m.