Triple
T27119625
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Panther City Lacrosse Club |
E686958
|
entity |
| Predicate | inceptionAsExpansionFranchise |
P53292
|
FINISHED |
| Object | July 2020 |
—
|
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: July 2020 | Statement: [Panther City Lacrosse Club, inceptionAsExpansionFranchise, July 2020]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inceptionAsExpansionFranchise Context triple: [Panther City Lacrosse Club, inceptionAsExpansionFranchise, July 2020]
-
A.
inceptionAsFranchise
chosen
Indicates that one entity marks the starting point or origin of another entity as a franchise.
-
B.
inceptionSeason
Indicates the season in which something (such as a series, competition, or activity) first began or was introduced.
-
C.
inceptionPart
Indicates that one entity represents a component, segment, or phase within the initial creation or starting process of another entity.
-
D.
inception
Indicates the point in time or event at which something begins, originates, or is first established.
-
E.
inceptionAsFort
Indicates that an entity was originally established or came into existence as a fort.
- 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_69ef148c2b588190afc15b529f7af845 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f624421d188190a5356a4596df536e |
completed | May 2, 2026, 4:20 p.m. |
| PD | Predicate disambiguation | batch_69f61b40f02081909bd9c3ea73249163 |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 8:58 a.m.