Triple
T13969316
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greg Page |
E336010
|
entity |
| Predicate | resultOfCroweFight |
P19109
|
FINISHED |
| Object | lost by technical knockout |
—
|
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: lost by technical knockout | Statement: [Greg Page, resultOfCroweFight, lost by technical knockout]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resultOfCroweFight Context triple: [Greg Page, resultOfCroweFight, lost by technical knockout]
-
A.
outcomeOf
Indicates that one entity is the result, consequence, or product that arises from another entity, event, or process.
-
B.
resultOfBattle
chosen
Indicates that one entity is the outcome or consequence produced by a specific battle or combat event involving another entity.
-
C.
crashResultedIn
Indicates that a crash event caused or led to a particular outcome, consequence, or result.
-
D.
resultOfMatch
Indicates that one entity is the outcome or product produced by a particular match or matching event involving another entity.
-
E.
wasBeaten
Indicates that one entity defeated or physically overpowered another in a contest, conflict, or confrontation.
- 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_69d81c61f3508190aaf2ca0dc0002c59 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2e8daeac8190aadd4b3b60222482 |
completed | April 14, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69dd465a21408190b912a42c50ffa0d9 |
completed | April 13, 2026, 7:39 p.m. |
Created at: April 9, 2026, 10:18 p.m.