Triple
T17322779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | earl (British peerage) |
E420601
|
entity |
| Predicate | preNormanEquivalent |
P126998
|
FINISHED |
| Object | ealdorman |
—
|
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: ealdorman | Statement: [earl (British peerage), preNormanEquivalent, ealdorman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preNormanEquivalent Context triple: [earl (British peerage), preNormanEquivalent, ealdorman]
-
A.
normativeFormUntil
Indicates that a particular normative form or standard applies to something only up to a specified point in time, after which it is no longer in effect.
-
B.
normativeFor
Indicates that something establishes, prescribes, or encodes the norms, standards, or rules that should govern another thing’s behavior or state.
-
C.
oftenNormalizedTo
Indicates that one entity is frequently converted, mapped, or standardized into the form or representation of another entity.
-
D.
norseEquivalent
Indicates that one entity is the counterpart or analogue of another within Norse mythology or Norse cultural context.
-
E.
hasNorm
Indicates that an entity is associated with, governed by, or characterized through a particular norm, rule, or standard.
- F. None of above. chosen
Provenance (4 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_69d889d22b848190a4663d0b8f8f76e7 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e439d01e2c8190a358dace420d4575 |
completed | April 19, 2026, 2:11 a.m. |
| PD | Predicate disambiguation | batch_69e3b01b9d1c8190a406dd941c9b11a1 |
completed | April 18, 2026, 4:23 p.m. |
| PDg | Predicate description generation | batch_69e3b2a225b08190a50f984caa6513b9 |
completed | April 18, 2026, 4:34 p.m. |
Created at: April 10, 2026, 5:43 a.m.