Triple
T7187792
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Left |
E167613
|
entity |
| Predicate | hasCoreFocus |
P10167
|
FINISHED |
| Object | class struggle |
—
|
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: class struggle | Statement: [Old Left, hasCoreFocus, class struggle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoreFocus Context triple: [Old Left, hasCoreFocus, class struggle]
-
A.
hasProgramFocus
Indicates that an entity (such as a program or initiative) is oriented around or primarily concerned with a particular thematic area, topic, or objective.
-
B.
hasPrimaryFocus
chosen
Indicates that something is the main subject, concern, or area of attention for an entity or activity.
-
C.
hasCore
Indicates that one entity possesses, contains, or is built around a central or most essential component represented by another entity.
-
D.
hasGlobalFocus
Indicates that something is oriented toward, concerned with, or applicable to worldwide or international scope rather than a local or regional one.
-
E.
hasSecondaryFocus
Indicates that an entity has an additional, subordinate area of attention, concern, or specialization beyond its primary focus.
- 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_69c6888b5248819090499a884ee3ec39 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e8e2506881909fc4e81b9b79e873 |
completed | March 27, 2026, 8:30 p.m. |
| PD | Predicate disambiguation | batch_69c6e752385c819096fbab55566ee2a8 |
completed | March 27, 2026, 8:23 p.m. |
Created at: March 27, 2026, 2:50 p.m.