Triple
T29061536
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Union of Vilnius and Radom |
E735548
|
entity |
| Predicate | definedTitleAs |
P47620
|
FINISHED |
| Object | Grand Duke of Lithuania |
—
|
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: Grand Duke of Lithuania | Statement: [Union of Vilnius and Radom, definedTitleAs, Grand Duke of Lithuania]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definedTitleAs Context triple: [Union of Vilnius and Radom, definedTitleAs, Grand Duke of Lithuania]
-
A.
namedForTitle
Indicates that one entity is named after or in honor of the title (such as a rank, honorific, or formal designation) associated with another entity.
-
B.
usesTitleIn
Indicates that an entity is referred to using a particular title within a specified context or medium.
-
C.
providedTitle
chosen
Indicates that one entity has supplied or assigned a specific title or designation to another entity.
-
D.
definesHeadTitle
Indicates that one entity specifies or assigns the official head title or primary designation for another entity.
-
E.
usesTitle
Indicates that one entity refers to or addresses another entity using a specific title or formal designation.
- 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_69f077e85498819088b65186550da8cd |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69fb563aec448190875410fb1a3ed624 |
completed | May 6, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_69fb35b9ede881908aaae93a215525df |
completed | May 6, 2026, 12:36 p.m. |
Created at: April 28, 2026, 10:15 a.m.