Triple
T8335911
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quidditch |
E195784
|
entity |
| Predicate | matchEndCondition |
P29156
|
FINISHED |
| Object | Golden Snitch is caught |
—
|
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: Golden Snitch is caught | Statement: [Quidditch, matchEndCondition, Golden Snitch is caught]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: matchEndCondition Context triple: [Quidditch, matchEndCondition, Golden Snitch is caught]
-
A.
terminationCondition
chosen
Indicates the condition or set of conditions under which an ongoing process, activity, or relationship is brought to an end.
-
B.
terminalCondition
Indicates the condition or set of conditions under which a process, interaction, or state is considered complete and should terminate.
-
C.
captureCondition
Indicates the specific circumstances or criteria under which a capture event or action is triggered or considered valid.
-
D.
hasConditionalEnding
Indicates that one entity concludes or terminates only if a specified condition involving another entity is met.
-
E.
matchResult
Indicates the outcome or final status produced by a particular match or game between participants.
- 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_69ca82ecbdc481908a55cad8ca062d88 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7fd3fc80819097b326119107ad4d |
completed | March 31, 2026, 8:03 a.m. |
| PD | Predicate disambiguation | batch_69cb70c3231c81909e3d463192c9de22 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:57 p.m.