Triple
T6522784
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brandon |
E151225
|
entity |
| Predicate | etymologyElement |
P453
|
FINISHED |
| Object | Old English "brom" (broom, gorse) |
—
|
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: Old English "brom" (broom, gorse) | Statement: [Brandon, etymologyElement, Old English "brom" (broom, gorse)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: etymologyElement Context triple: [Brandon, etymologyElement, Old English "brom" (broom, gorse)]
-
A.
etymologyType
Indicates the specific kind or category of etymological relationship that links a term to its linguistic origin or source.
-
B.
etymology
chosen
Indicates the historical origin and development of a word or term, including its source language and form.
-
C.
etymologyStatus
Indicates the status or reliability classification of an etymological explanation for a term or name.
-
D.
etymologicalField
Indicates that one term belongs to a particular semantic or conceptual domain relevant to its etymological origin or historical development.
-
E.
etymologyGloss
Indicates that a term’s meaning is explained by a brief gloss specifically describing its etymological origin or source.
- 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_69c687f522748190b3058405553cdabd |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6ad95c2c88190b800aaaa73f99210 |
completed | March 27, 2026, 4:17 p.m. |
| PD | Predicate disambiguation | batch_69c68abbc7148190a8270d47fe10cc31 |
completed | March 27, 2026, 1:48 p.m. |
Created at: March 27, 2026, 1:45 p.m.