Triple
T134302
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SU |
E2716
|
entity |
| Predicate | politicalAssociation |
P4806
|
FINISHED |
| Object | communist state bloc (historical) |
—
|
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: communist state bloc (historical) | Statement: [SU, politicalAssociation, communist state bloc (historical)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: politicalAssociation Context triple: [SU, politicalAssociation, communist state bloc (historical)]
-
A.
politicalParty
Indicates that an entity is affiliated with, belongs to, or is a member of a specific political party.
-
B.
politicalFunction
Indicates that an entity holds, performs, or is associated with a specific role, duty, or function within a political system or structure.
-
C.
politicalPattern
Indicates a recurring or characteristic way in which political behaviors, decisions, or power dynamics are organized or expressed.
-
D.
politicalSupporter
chosen
Indicates that one entity supports, endorses, or aligns with the political views, actions, or position of another entity.
-
E.
endedPoliticalEntity
Indicates that one political entity brought about the termination or dissolution of another political 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_69a2520c0f3481908b0ed054a2fca8d0 |
completed | Feb. 28, 2026, 2:25 a.m. |
| NER | Named-entity recognition | batch_69a25788b2688190a45b39447f702551 |
completed | Feb. 28, 2026, 2:48 a.m. |
| PD | Predicate disambiguation | batch_69a25650251c81908a6ea6368cd61198 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:30 a.m.