Triple
T18671761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bretwalda |
E456492
|
entity |
| Predicate | meaningEtymology |
P15774
|
FINISHED |
| Object | possibly "wide-ruler" or "Britain-ruler" |
—
|
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: possibly "wide-ruler" or "Britain-ruler" | Statement: [Bretwalda, meaningEtymology, possibly "wide-ruler" or "Britain-ruler"]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: meaningEtymology Context triple: [Bretwalda, meaningEtymology, possibly "wide-ruler" or "Britain-ruler"]
-
A.
etymologicalRootMeaning
Indicates that one term’s meaning originates from or is derived from the historical or original meaning of another term.
-
B.
etymologyPossibleMeaning
chosen
Indicates a possible or hypothesized meaning that an etymological analysis suggests for a word or term.
-
C.
ermenMeaning
Indicates that one entity represents or conveys the meaning or semantic interpretation of another entity.
-
D.
etymologyGloss
Indicates that a term’s meaning is explained by a brief gloss specifically describing its etymological origin or source.
-
E.
etymology
Indicates the historical origin and development of a word or term, including its source language and form.
- 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_69d8d38f72b4819090a935175d9ca8af |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e556b21d2481908e1b8b583bfabb72 |
completed | April 19, 2026, 10:26 p.m. |
| PD | Predicate disambiguation | batch_69e478db7a248190a8c6584673773923 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:48 a.m.