Triple
T27461341
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Workers’ Opposition |
E692752
|
entity |
| Predicate | authorOfProgrammaticText |
P177111
|
FINISHED |
| Object | Alexandra Kollontai |
—
|
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: Alexandra Kollontai | Statement: [Workers’ Opposition, authorOfProgrammaticText, Alexandra Kollontai]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: authorOfProgrammaticText Context triple: [Workers’ Opposition, authorOfProgrammaticText, Alexandra Kollontai]
-
A.
theoreticalTextAuthor
Indicates that one entity is the author or creator of a theoretical or conceptual text associated with the other entity.
-
B.
languageAuthor
Indicates that an entity is the creator or originator of a particular language.
-
C.
composerOfTextSetting
Indicates that one entity is the composer who created the musical setting for a text associated with another entity.
-
D.
actuallyWrittenBy
Indicates that the specified work was in fact authored by the given entity, possibly correcting or overriding a previously assumed or credited author.
-
E.
canonicalAuthor
Indicates that an entity is the officially recognized or standard author of a given work or resource.
- F. None of above. chosen
Provenance (4 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_69ef5207903881909427745cda05d27a |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f6f85bfba48190aba95b40642a8ca7 |
completed | May 3, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f6f65fd1d08190b88e5e68ba268500 |
completed | May 3, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69f6f854486c81909396d944a55e03ab |
completed | May 3, 2026, 7:25 a.m. |
Created at: April 27, 2026, 12:50 p.m.