Triple
T30009930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince of Galicia–Volhynia |
E762428
|
entity |
| Predicate | titleHigherOrEqualTo |
P35573
|
FINISHED |
| Object | Prince of Galicia |
—
|
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: Prince of Galicia | Statement: [Prince of Galicia–Volhynia, titleHigherOrEqualTo, Prince of Galicia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleHigherOrEqualTo Context triple: [Prince of Galicia–Volhynia, titleHigherOrEqualTo, Prince of Galicia]
-
A.
higherTitleOf
Indicates that one entity holds a job or position title that is hierarchically superior to the title held by another entity.
-
B.
titleAfterElevation
Indicates the formal title or designation an entity receives following a promotion, elevation in rank, or change in status.
-
C.
titleHolderIs
Indicates that one entity currently holds or possesses a specific title associated with another entity.
-
D.
isHigherThan
Indicates that one entity has a greater value, level, or position than another entity.
-
E.
titleHierarchy
chosen
Indicates a hierarchical relationship between titles, where one title is ranked above or below another in an ordered structure.
- 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_69f2246b0c84819094f1250b6a02d277 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fd8ccbd4c88190b13aae0673b3c821 |
completed | May 8, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69fd8ae2227c819089546f5c3629799e |
completed | May 8, 2026, 7:04 a.m. |
Created at: April 29, 2026, 6:43 p.m.