Triple
T28686277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kingdom of Surrey |
E729140
|
entity |
| Predicate | partiallyAbsorbedBy |
P64654
|
FINISHED |
| Object | Kingdom of Mercia |
—
|
NE NERFINISHED |
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: Kingdom of Mercia | Statement: [Kingdom of Surrey, partiallyAbsorbedBy, Kingdom of Mercia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partiallyAbsorbedBy Context triple: [Kingdom of Surrey, partiallyAbsorbedBy, Kingdom of Mercia]
-
A.
partiallyOn
Indicates that one entity rests or extends over another such that only a portion of its area, volume, or length is supported or in contact.
-
B.
isPartially
Indicates that one entity is included within another to some extent, but not completely or fully.
-
C.
partiallyEnclosed
Indicates that one entity surrounds or covers another entity to some extent, but not completely.
-
D.
absorbed
Indicates that one entity takes in, soaks up, or assimilates another entity or substance.
-
E.
partiallyIncorporatedInto
chosen
Indicates that one entity has been integrated or absorbed into another entity, but only to a limited or incomplete extent.
- 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_69f043e60b6c8190ac2cd042e77fe6e9 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f6c49627908190b3553474c7c3072b |
completed | May 3, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f23ae081909a52801266063a3c |
completed | May 3, 2026, 3:41 a.m. |
Created at: April 28, 2026, 5:32 a.m.