Triple
T37364072
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oiscingas |
E927660
|
entity |
| Predicate | hasAllegedAncestor |
P149753
|
FINISHED |
| Object | Hengist |
—
|
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: Hengist | Statement: [Oiscingas, hasAllegedAncestor, Hengist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAllegedAncestor Context triple: [Oiscingas, hasAllegedAncestor, Hengist]
-
A.
allegedAncestor
chosen
Indicates that one entity is claimed or suspected to be an ancestor of another, without confirming that the ancestral relationship is true.
-
B.
hasAllegedRelationshipWith
Indicates a claimed or suspected relationship between two entities that is not confirmed as factual.
-
C.
alsoHasAncestry
Indicates that an entity possesses an additional ancestral lineage or heritage beyond its primary recorded ancestry.
-
D.
hasTribalAncestor
Indicates that an entity is descended from, or has lineage tracing back to, a specified tribal ancestor.
-
E.
hasFamilialTieTo
Indicates a relationship where two entities are connected by family bonds, such as by blood, marriage, or adoption.
- 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_69f76eb701788190b40824bc4594d985 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fe6fea4a288190bf8615c5d6bf41b4 |
completed | May 8, 2026, 11:21 p.m. |
| PD | Predicate disambiguation | batch_69fe6f774de08190975a2393b9a1fd22 |
completed | May 8, 2026, 11:19 p.m. |
Created at: May 3, 2026, 4:16 p.m.