Triple
T35809791
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pedigree |
E1035197
|
entity |
| Predicate | oftenUsedToFinish |
P185082
|
FINISHED |
| Object | main event matches |
—
|
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: main event matches | Statement: [Pedigree, oftenUsedToFinish, main event matches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenUsedToFinish Context triple: [Pedigree, oftenUsedToFinish, main event matches]
-
A.
oftenFinishedWith
Indicates that one action, event, or process is frequently concluded or brought to an end by another specified action, event, or process.
-
B.
usesFinishType
chosen
Indicates that one entity employs or is associated with a particular type of finish or finishing method in relation to another entity.
-
C.
finisherCategory
Indicates the classification or type assigned to how something is finished or completed (e.g., style, method, or outcome of a finishing action).
-
D.
finisher
Indicates that an entity completes, concludes, or brings to an end a process, event, or sequence, often as the final actor or decisive contributor.
-
E.
finishingMethod
Indicates the technique or process used to complete or finalize an object, task, or work.
- 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_69f76e1762408190b885a8456862e372 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fdbc5ef46c8190bbcfb9798f4615b7 |
completed | May 8, 2026, 10:35 a.m. |
| PD | Predicate disambiguation | batch_69fdbb270338819082ce3f73903e884f |
completed | May 8, 2026, 10:29 a.m. |
Created at: May 3, 2026, 4:06 p.m.