Triple
T11613597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Penn FC |
E275444
|
entity |
| Predicate | announcedHiatusFromUSL |
P54927
|
FINISHED |
| Object | 2018 |
—
|
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: 2018 | Statement: [Penn FC, announcedHiatusFromUSL, 2018]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: announcedHiatusFromUSL Context triple: [Penn FC, announcedHiatusFromUSL, 2018]
-
A.
announcedHiatus
chosen
Indicates that an entity has publicly declared a temporary pause or suspension in its usual activities or operations.
-
B.
tookHiatusFromWNBAInYear
Indicates that a person temporarily stopped playing or participating in the WNBA during a specified year.
-
C.
discontinuationAnnouncedBy
Indicates that an entity’s discontinuation (e.g., of a product, service, or activity) has been formally announced by a specific agent or organization.
-
D.
announcedPermanentClosure
Indicates that an entity has formally stated that it will cease operations or availability indefinitely and not reopen.
-
E.
discontinuationDateNorthAmerica
Indicates the date on which something stops being available or in use specifically within North America.
- 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_69d6aaf84b548190ac072e4fb89ae18f |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a044a3088190b92f4674c2d0b443 |
completed | April 10, 2026, 7:01 a.m. |
| PD | Predicate disambiguation | batch_69d85dd6503c819081f9045e9d5c4f3f |
completed | April 10, 2026, 2:17 a.m. |
Created at: April 8, 2026, 9:38 p.m.