Triple
T22448608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Memphis Rogues |
E554928
|
entity |
| Predicate | playedInNASLSeason |
P148235
|
FINISHED |
| Object | 1978 NASL season |
—
|
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: 1978 NASL season | Statement: [Memphis Rogues, playedInNASLSeason, 1978 NASL season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playedInNASLSeason Context triple: [Memphis Rogues, playedInNASLSeason, 1978 NASL season]
-
A.
playedForMLSClub
Indicates that a person has been a player on the roster of a club that competes in Major League Soccer (MLS).
-
B.
seasonNumberInNASLModernEra
Indicates the specific numbered season an event or competition falls into within the modern era of the NASL (North American Soccer League).
-
C.
playedFor
Indicates that one entity has been a member of or participated as a player for a particular team, organization, or group.
-
D.
seasonCountInNASL
Indicates the number of seasons an entity participated in the NASL (North American Soccer League).
-
E.
leagueParticipatedInAsPlayer
Indicates that a person, in the role of a player, took part in competitions organized by a specific league.
- 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_69e11e5113208190ab58c6b595f9d1d0 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15b4a20f8819097f471084e97e099 |
completed | April 29, 2026, 1:13 a.m. |
| PD | Predicate disambiguation | batch_69e898ad961c819098fd1e46129bddcc |
completed | April 22, 2026, 9:45 a.m. |
| PDg | Predicate description generation | batch_69e8aa39e3388190b659d59948ebf3e6 |
completed | April 22, 2026, 11 a.m. |
Created at: April 16, 2026, 8:48 p.m.