Triple
T13162215
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Pennsylvania |
E312754
|
entity |
| Predicate | playoffImportance |
P10402
|
FINISHED |
| Object | multiple playoff meetings |
—
|
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: multiple playoff meetings | Statement: [Battle of Pennsylvania, playoffImportance, multiple playoff meetings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playoffImportance Context triple: [Battle of Pennsylvania, playoffImportance, multiple playoff meetings]
-
A.
playoffImplications
chosen
Indicates that the outcome of a game or event has a direct effect on qualification, seeding, or progression within a playoff structure.
-
B.
finalMatchImportance
Indicates the degree of significance or impact assigned to the final match within a competition or event.
-
C.
playoffContext
Indicates that the relationship or action occurs within the setting or circumstances of a playoff or postseason competition.
-
D.
playoffPoints
Indicates the number of points an entity has earned or been credited with in playoff or postseason competition.
-
E.
hasRegularSeasonImportance
Indicates that something possesses significance or relevance specifically within the context of a regular season.
- 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_69d806ac3ee081909b2fd27d060aa974 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf054f88190b05ced98d5a22a62 |
completed | April 10, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69d98bbd1d088190b7c69f37fc6eeb64 |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:12 p.m.