Triple
T35532608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ekkeharding dynasty |
E1026841
|
entity |
| Predicate | roleInFrontier |
P203270
|
FINISHED |
| Object | defense against Slavic tribes |
—
|
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: defense against Slavic tribes | Statement: [Ekkeharding dynasty, roleInFrontier, defense against Slavic tribes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInFrontier Context triple: [Ekkeharding dynasty, roleInFrontier, defense against Slavic tribes]
-
A.
roleInElysium
Indicates that an entity holds a specific role, position, or function within the context of Elysium.
-
B.
roleInDUNE
Indicates that an entity has a specific acting role or participation in the production of the film "Dune."
-
C.
roleInExpedition
Indicates the specific function, duty, or position an entity holds within the context of a particular expedition.
-
D.
roleInNewHorizons
Indicates that an entity has a specific role or function within the context of the "New Horizons" project, mission, or initiative.
-
E.
roleInTranscendence
Indicates that an entity plays a specific role or function in another entity’s process, state, or act of transcendence.
- 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_69f76dff7e508190b28ceeee770dce23 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a0144c75aec81908bdd9e88f2af737a |
completed | May 11, 2026, 2:53 a.m. |
| PD | Predicate disambiguation | batch_6a014405a2d48190a1d58b0b907ad696 |
completed | May 11, 2026, 2:50 a.m. |
| PDg | Predicate description generation | batch_6a0144c6bd20819093562eb03dc5b2c8 |
completed | May 11, 2026, 2:53 a.m. |
Created at: May 3, 2026, 4:04 p.m.