Triple
T27005755
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1987 New York Mets season |
E680235
|
entity |
| Predicate | attemptedToRepeatAs |
P162027
|
FINISHED |
| Object | World Series champions |
—
|
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: World Series champions | Statement: [1987 New York Mets season, attemptedToRepeatAs, World Series champions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attemptedToRepeatAs Context triple: [1987 New York Mets season, attemptedToRepeatAs, World Series champions]
-
A.
replacedEarlierAttempts
Indicates that a current attempt has superseded and taken the place of one or more previous attempts made earlier.
-
B.
repetitionOf
Indicates that one entity is a repeated occurrence or instance of another entity, preserving the same content or pattern.
-
C.
wasTriedAfter
Indicates that one trial or legal proceeding occurred subsequent to another in time.
-
D.
attemptNumber
Indicates the specific ordinal count of attempts made for a given action or process.
-
E.
triedAt
Indicates that an attempt to perform an action or achieve an outcome occurred at a specific time or place.
- F. None of above. chosen
Provenance (4 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_69eeeb53939c8190bd431f32b060f01f |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f622abdfac8190988421c946411d7e |
completed | May 2, 2026, 4:13 p.m. |
| PD | Predicate disambiguation | batch_69f620e0b37481909a280574decbd443 |
completed | May 2, 2026, 4:05 p.m. |
| PDg | Predicate description generation | batch_69f621c7d3e0819095b1f327637ae4f9 |
completed | May 2, 2026, 4:09 p.m. |
Created at: April 27, 2026, 7 a.m.