Triple
T19400967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ginger |
E485321
|
entity |
| Predicate | hasPoliticalConcern |
P109963
|
FINISHED |
| Object | feminism |
—
|
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: feminism | Statement: [Ginger, hasPoliticalConcern, feminism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPoliticalConcern Context triple: [Ginger, hasPoliticalConcern, feminism]
-
A.
hasPoliticalComponent
chosen
Indicates that something includes, involves, or is influenced by political factors, interests, or considerations.
-
B.
strategicConcernFor
Indicates a relationship where one entity considers another entity’s situation, actions, or outcomes important for its own long-term goals, risks, or strategic interests.
-
C.
politicalIssueIn
Indicates that a political issue is relevant to, occurs within, or is associated with a particular geographic or political region.
-
D.
raisedConcernAbout
Indicates that one entity has expressed worry, doubt, or objection regarding another entity or issue.
-
E.
concernsWarBetween
Indicates a relationship where something (such as a statement, document, or event) is about or pertains to a war occurring between two or more parties.
- 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_69d8e8d5162481909db12435d9535c1a |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e62577454c81909d5bcd07e99b27e4 |
completed | April 20, 2026, 1:09 p.m. |
| PD | Predicate disambiguation | batch_69e4fd68b1f881908d273de1fee81a75 |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:36 p.m.