Triple
T16771523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scottish Miners' Federation |
E407607
|
entity |
| Predicate | representedProfession |
P10888
|
FINISHED |
| Object | miners |
—
|
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: miners | Statement: [Scottish Miners' Federation, representedProfession, miners]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: representedProfession Context triple: [Scottish Miners' Federation, representedProfession, miners]
-
A.
representedOccupation
chosen
Indicates that one entity has served as an official or formal representative of another entity’s occupation or professional role.
-
B.
memberProfession
Indicates that a member or individual holds or practices a particular profession or occupation.
-
C.
leftProfession
Indicates that an entity has stopped or abandoned a particular profession or occupation they previously held.
-
D.
includesProfession
Indicates that one entity’s set of attributes, roles, or members contains a specific profession as part of it.
-
E.
portraysProfession
Indicates that one entity depicts or represents another entity in a specific profession or occupational role.
- 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_69d8839174188190909f190097207065 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3b0361e5081908f58edf766ff3ce0 |
completed | April 18, 2026, 4:24 p.m. |
| PD | Predicate disambiguation | batch_69e319cbd79c8190a03587a61c18bec0 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:21 a.m.