Triple
T35670298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Steimer |
E1030695
|
entity |
| Predicate | hasNotableAnarchist |
P207088
|
FINISHED |
| Object | Mollie Steimer |
E315819
|
NE 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: Mollie Steimer | Statement: [Steimer, hasNotableAnarchist, Mollie Steimer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableAnarchist Context triple: [Steimer, hasNotableAnarchist, Mollie Steimer]
-
A.
notableDissident
Indicates that a person is recognized for actively opposing or resisting an established authority, regime, or dominant ideology in a notable or prominent way.
-
B.
hasNotablePolis
Indicates that an entity is associated with or contains a city-state (polis) that is considered notable or significant.
-
C.
hasNotableActivistBackground
Indicates that an entity is known for a significant history of involvement in activism or social/political advocacy.
-
D.
hasNotableMember
Indicates that a group, organization, or collection includes at least one member who is distinguished or noteworthy in some significant way.
-
E.
notableProponent
Indicates that an entity is a well-known advocate or supporter of another entity, idea, or practice.
- F. None of above. chosen
Provenance (5 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_69f76e0acfc0819082c8495c2210ce73 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a387d0476c88190982bad0ca9b3c084 |
completed | June 22, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_6a037a04d8348190a4819666eab42c9b |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82179081908325a59b8539b3a8 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:05 p.m.