Triple
T15580659
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | November Bravo Sierra Echo |
E374484
|
entity |
| Predicate | correspondsToLetters |
P44428
|
FINISHED |
| Object | N |
—
|
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: N | Statement: [November Bravo Sierra Echo, correspondsToLetters, N]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: correspondsToLetters Context triple: [November Bravo Sierra Echo, correspondsToLetters, N]
-
A.
correspondsToEnglishLetter
Indicates that one entity is the English alphabet letter that matches, represents, or is equivalent to the other entity.
-
B.
correspondsToLatinLetter
chosen
Indicates that one entity is the counterpart or representation of another entity as a specific letter in the Latin alphabet.
-
C.
hasLettersFor
Indicates that one entity possesses or contains written correspondence intended for another entity.
-
D.
correspondsToPhoenicianLetter
Indicates a relationship where one written symbol or character is associated with, or derived from, a specific letter of the Phoenician alphabet.
-
E.
hasLetterBy
Indicates that an entity possesses or is associated with a letter authored or sent by another entity.
- 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_69d85ccd575081908909b71a3f3e3a61 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04e24064c8190b132c3092877fbfa |
completed | April 16, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_69deda817e9881909b0c66fc9056f7d5 |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:11 a.m.