Triple
T4263269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Gatlin Boys |
E96153
|
entity |
| Predicate | resolutionOutcome |
P21258
|
FINISHED |
| Object | physically defeated by Tommy |
—
|
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: physically defeated by Tommy | Statement: [The Gatlin Boys, resolutionOutcome, physically defeated by Tommy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resolutionOutcome Context triple: [The Gatlin Boys, resolutionOutcome, physically defeated by Tommy]
-
A.
resolution
Indicates the act of formally deciding, settling, or expressing a determined stance on an issue, often through an official decision or statement.
-
B.
resolutionEvent
Indicates an event or action through which a previously existing issue, conflict, or problem is brought to a conclusion or resolved.
-
C.
resolutionType
chosen
Indicates the specific manner or category by which an issue, event, or conflict is resolved or brought to a conclusion.
-
D.
resolutionMethod
Indicates the specific approach, technique, or process used to resolve a problem, conflict, or issue.
-
E.
resolvedIn
Indicates that an issue, conflict, or process is brought to a conclusion or solution within a specified context, medium, or timeframe.
- 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_69b3454095ac81909c2494f7ff294af1 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34fc821ec8190a7204aaf89d24a6b |
completed | March 12, 2026, 11:44 p.m. |
| PD | Predicate disambiguation | batch_69b347f8dcb08190a725c1f7fb5a7466 |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:06 p.m.