Triple
T26924763
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Intel Grand Slam |
E677746
|
entity |
| Predicate | secondCompletedBy |
P65318
|
FINISHED |
| Object | Team Liquid |
—
|
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: Team Liquid | Statement: [Intel Grand Slam, secondCompletedBy, Team Liquid]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondCompletedBy Context triple: [Intel Grand Slam, secondCompletedBy, Team Liquid]
-
A.
alsoCompletedBy
chosen
Indicates that the same task, activity, or item has been completed by an additional agent or entity besides the one already referenced.
-
B.
secondPhaseCompletion
Indicates that a process, project, or operation has finished its second phase or stage.
-
C.
secondStageCompletionDate
Indicates the date on which the second stage of a process, project, or workflow is completed.
-
D.
completedBy
Indicates that a task, process, or action has been finished or carried out by a particular entity.
-
E.
completedAfter
Indicates that one event or task was finished at a later time than another specified event or task.
- 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_69eee9bdebc48190ba90a12a63e09c73 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f7431c0eec81909ead443e07d75e18 |
completed | May 3, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69f74143cf708190a12d487884298437 |
completed | May 3, 2026, 12:36 p.m. |
Created at: April 27, 2026, 6:09 a.m.