Triple
T28288485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Billy McNeill |
E713353
|
entity |
| Predicate | testimonialMatch |
P1460
|
FINISHED |
| Object | Celtic vs Liverpool 1974 |
—
|
NE NERFINISHED |
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: Celtic vs Liverpool 1974 | Statement: [Billy McNeill, testimonialMatch, Celtic vs Liverpool 1974]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: testimonialMatch Context triple: [Billy McNeill, testimonialMatch, Celtic vs Liverpool 1974]
-
A.
testedPerson
Indicates that one entity has been subjected to a test, examination, or evaluation involving another entity.
-
B.
testimonyCharacteristic
Indicates that a particular quality, feature, or attribute is being ascribed to a testimony or statement given by an entity.
-
C.
correspondsWith
Indicates that two entities are in mutual alignment or agreement, such that one matches, parallels, or is equivalent to the other in a specified respect.
-
D.
confirmedBy
Indicates that one entity validates, approves, or verifies the truth, accuracy, or occurrence of another entity or event.
-
E.
matches
chosen
Indicates that two entities correspond to or are in agreement with each other according to some defined criteria or pattern.
- 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_69efb52371d88190a1381c4e58a3b731 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f65a6c900881908f18b61273d7bf8d |
completed | May 2, 2026, 8:11 p.m. |
| PD | Predicate disambiguation | batch_69f659ce58408190ba9e007b4810d4d0 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 27, 2026, 11:27 p.m.