Triple
T17111331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anglo-Saxon nobility |
E415231
|
entity |
| Predicate | socialRankAbove |
P60246
|
FINISHED |
| Object | ceorls |
—
|
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: ceorls | Statement: [Anglo-Saxon nobility, socialRankAbove, ceorls]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: socialRankAbove Context triple: [Anglo-Saxon nobility, socialRankAbove, ceorls]
-
A.
sharesRankWith
Indicates that two entities have the same rank or hierarchical level within a given ordering or classification.
-
B.
socialPosition
chosen
Indicates the relative social status, rank, or standing one entity holds within a social hierarchy or structure in relation to others.
-
C.
rankComparedTo
Indicates the relative ordering or position of one entity in comparison to another based on a specified ranking criterion.
-
D.
rankedAmong
Indicates that an entity holds a specific position or status within a defined group, list, or hierarchy of comparable entities.
-
E.
isHighRanking
Indicates that an entity holds a position of relatively great authority, status, or seniority within a hierarchy or organization.
- 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_69d886d090cc8190a39cb94992586905 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dc2a7f2c81908eb19594b6accab7 |
completed | April 18, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69e35d6b1b988190a8d6b6fe78c35e59 |
completed | April 18, 2026, 10:31 a.m. |
Created at: April 10, 2026, 5:35 a.m.