Triple
T15001237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Czechoslovak centralist parties |
E374093
|
entity |
| Predicate | mainlyRepresented |
P86059
|
FINISHED |
| Object | Czech political elites |
—
|
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: Czech political elites | Statement: [Czechoslovak centralist parties, mainlyRepresented, Czech political elites]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainlyRepresented Context triple: [Czechoslovak centralist parties, mainlyRepresented, Czech political elites]
-
A.
primarilyRepresentedBy
chosen
Indicates that one entity serves as the main or most characteristic representation or depiction of another entity.
-
B.
representedFor
Indicates that one entity has acted or served as the official representative or proxy on behalf of another entity.
-
C.
areRepresentedBy
Indicates that one entity serves as a representation, proxy, or stand-in for another entity.
-
D.
majorRepresentative
Indicates that one entity serves as the primary or main representative of another entity.
-
E.
nationalityRepresented
Indicates the country or nation that an entity officially represents, typically in a professional, competitive, or diplomatic capacity.
- 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_69d85ccc84388190aa151e5173370c8d |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded72fec948190b1c9705538c57976 |
completed | April 15, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_69de9a6531a88190acde65199a477350 |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:54 a.m.