Triple
T27398968
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andrew Holbrook |
E691775
|
entity |
| Predicate | hasWinMethod |
P154896
|
FINISHED |
| Object | submission |
—
|
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: submission | Statement: [Andrew Holbrook, hasWinMethod, submission]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWinMethod Context triple: [Andrew Holbrook, hasWinMethod, submission]
-
A.
hasWonByMethod
chosen
Indicates that one party has achieved victory over another through a specified method or manner of winning.
-
B.
hasWinningCondition
Indicates that a particular condition or set of conditions determines when a participant, entity, or process is considered to have won or successfully completed a defined objective.
-
C.
hasWorkingMethod
Indicates that one entity possesses or employs a functional method, procedure, or technique to achieve a particular task or outcome.
-
D.
hasPlayingMethod
Indicates that there is a specific way, technique, or method by which something is played or performed.
-
E.
hasAccessMethod
Indicates that one entity uses or is associated with a particular method or mechanism for accessing another entity or resource.
- 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_69ef5204f7048190bf226a129858fc5b |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c1f94ac8190bc6fbc7916fc0d82 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 27, 2026, 12:28 p.m.