Triple
T22490346
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Black Country derby |
E555998
|
entity |
| Predicate | earliestMeetings |
P105720
|
FINISHED |
| Object | late 19th century |
—
|
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: late 19th century | Statement: [Black Country derby, earliestMeetings, late 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earliestMeetings Context triple: [Black Country derby, earliestMeetings, late 19th century]
-
A.
dateOfFirstMeeting
Indicates the specific date on which two or more entities first met or came together.
-
B.
meetsSince
chosen
Indicates that two entities have been meeting with each other starting from a specific point in time and continuing thereafter.
-
C.
firstMeets
Indicates that one entity encounters or comes into contact with another entity for the first time.
-
D.
previouslyConveneAt
Indicates that an entity held or participated in a gathering, meeting, or session at a specified location or venue at some earlier time.
-
E.
convenesBefore
Indicates that one event or gathering is convened and completed before another specified event or gathering begins.
- 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_69e11e53897c819088863779f8c50bb0 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15c40930c81908310ac6afd98c62e |
completed | April 29, 2026, 1:17 a.m. |
| PD | Predicate disambiguation | batch_69e898b6eee08190ba673a0ee329e671 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:49 p.m.