Triple
T34902381
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lodomeria |
E1006626
|
entity |
| Predicate | linkedWithTitle |
P5175
|
FINISHED |
| Object | Kingdom of Galicia and Lodomeria |
—
|
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 Galicia and Lodomeria | Statement: [Lodomeria, linkedWithTitle, Kingdom of Galicia and Lodomeria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linkedWithTitle Context triple: [Lodomeria, linkedWithTitle, Kingdom of Galicia and Lodomeria]
-
A.
relatedTitleHolder
Indicates that one entity holds a title or position that is related or connected to the title or position held by another entity.
-
B.
linkedTitleFamily
Indicates that one title is associated with or belongs to the same family or grouping of related titles as another.
-
C.
linkTitleKey
Indicates that an entity serves as the title (or key title string) associated with a specific link or hyperlink.
-
D.
linkedDocument
Indicates that one document is associated with or references another document in a meaningful way.
-
E.
associatedTitle
chosen
Indicates that one entity has a title, designation, or formal label that is linked or relevant to another entity.
- 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_69f76dc1b4a081909b4c6e4d8ec0aa2d |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fe779248c081909f0ed1a2a0df23db |
completed | May 8, 2026, 11:53 p.m. |
| PD | Predicate disambiguation | batch_69fe76eaf6d48190998bc7168749cc42 |
completed | May 8, 2026, 11:51 p.m. |
Created at: May 3, 2026, 4 p.m.