Triple
T4104406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jersey Shore BlueClaws |
E88414
|
entity |
| Predicate | affiliationStartYear |
P38522
|
FINISHED |
| Object | 2001 |
—
|
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: 2001 | Statement: [Jersey Shore BlueClaws, affiliationStartYear, 2001]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: affiliationStartYear Context triple: [Jersey Shore BlueClaws, affiliationStartYear, 2001]
-
A.
affiliationStart
chosen
Indicates the point in time when an entity’s formal association or membership with another entity begins.
-
B.
conferenceAffiliationStart
Indicates the point in time when an entity’s affiliation with a particular conference begins.
-
C.
laterAffiliation
Indicates that an entity becomes affiliated with another entity at a later time than a previously mentioned or initial affiliation.
-
D.
affiliationHistory
Indicates a historical record of an entity’s past and present organizational or group affiliations, including when and how those affiliations changed over time.
-
E.
awardingBodyFoundedIn
Indicates the year or date when the awarding body (the organization that grants awards) was established or founded.
- 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_69aed9484fb881909146f4c772ad277c |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefd31bad88190b850d1dcba14de60 |
completed | March 9, 2026, 5:02 p.m. |
| PD | Predicate disambiguation | batch_69aef90b2ef08190ae84febfd69dd48b |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:40 p.m.