Triple
T6744356
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Government of the First Czechoslovak Republic |
E154170
|
entity |
| Predicate | hasStateHeadTitle |
P13335
|
FINISHED |
| Object | president of Czechoslovakia |
—
|
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: president of Czechoslovakia | Statement: [Government of the First Czechoslovak Republic, hasStateHeadTitle, president of Czechoslovakia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStateHeadTitle Context triple: [Government of the First Czechoslovak Republic, hasStateHeadTitle, president of Czechoslovakia]
-
A.
hasHeading
Indicates that one entity serves as a heading or title for another entity.
-
B.
hasTitleIn
Indicates that an entity holds or is associated with a specific title within a particular context, domain, or language.
-
C.
hasTitleFrom
Indicates that one entity holds or uses a title that originates from, or is conferred by, another entity.
-
D.
hadTitle
chosen
Indicates that an entity held or was assigned a specific title or formal designation.
-
E.
hasTitleSince
Indicates that an entity has held a particular title continuously starting from a specified point in time.
- 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_69c6880d84d8819095d19de2295f26ac |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d1b543688190af179e0244d1ff75 |
completed | March 27, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69c6d09067a0819087ed6c820f4699f8 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:10 p.m.