Triple
T7967012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Molinero |
E185229
|
entity |
| Predicate | historicalClassAssociation |
P66217
|
FINISHED |
| Object | working class |
—
|
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: working class | Statement: [Molinero, historicalClassAssociation, working class]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalClassAssociation Context triple: [Molinero, historicalClassAssociation, working class]
-
A.
historicallyLinked
Indicates that two entities are connected through a shared or related historical event, period, or development.
-
B.
historicalRegionAssociation
Indicates an association where an entity is or was located in, part of, or otherwise related to a specific historical region.
-
C.
modernAssociation
Indicates a contemporary or currently relevant connection, affiliation, or relationship between entities.
-
D.
historicalType
chosen
Indicates that one entity classifies or characterizes another in terms of its role, status, or category within a historical context.
-
E.
historicalClassificationEnd
Indicates the point in time when a particular historical classification or categorization of an entity ceases to be valid.
- 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_69ca8297699481909b75a405f01e03af |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3ba3f53c8190a0e9b3de2f1b9645 |
completed | March 31, 2026, 3:12 a.m. |
| PD | Predicate disambiguation | batch_69cb0473d7dc8190a25d0cf460b9fcbe |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:13 p.m.