Triple
T7000982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Solidarność |
E162335
|
entity |
| Predicate | coreDemand |
P7686
|
FINISHED |
| Object | independent trade unions |
—
|
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: independent trade unions | Statement: [Solidarność, coreDemand, independent trade unions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coreDemand Context triple: [Solidarność, coreDemand, independent trade unions]
-
A.
demand
Indicates that one entity requests or insists that another entity provide something or perform an action, often with an expectation of compliance.
-
B.
demands
chosen
Indicates that one entity insists that another entity provide something or take a specific action, typically with authority or urgency.
-
C.
demanded
Indicates that one entity forcefully or insistently requested something from another entity.
-
D.
technicalDemand
Indicates that one entity requires or imposes a certain level of technical skill, complexity, or resources on another entity.
-
E.
coreMarket
Indicates that an entity serves as the primary or most important market for another entity’s products, services, or activities.
- 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_69c68857ffc08190857dc62cd5253777 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6dc0f8830819091f4356296234713 |
completed | March 27, 2026, 7:35 p.m. |
| PD | Predicate disambiguation | batch_69c6d7c67c94819084fdcf0398606027 |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:33 p.m.