Triple
T36677943
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maidstone United F.C. |
E905593
|
entity |
| Predicate | foundedAsCurrentClub |
P199239
|
FINISHED |
| Object | 1992 |
—
|
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: 1992 | Statement: [Maidstone United F.C., foundedAsCurrentClub, 1992]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundedAsCurrentClub Context triple: [Maidstone United F.C., foundedAsCurrentClub, 1992]
-
A.
foundedAsClubInYear
Indicates that an organization was originally established as a club in the specified year.
-
B.
foundedAsClub
Indicates that an organization or entity was originally established in the form of a club.
-
C.
foundedAsTopLevelClub
Indicates that an organization was originally established directly as a top-tier club, rather than being promoted or restructured from a lower level.
-
D.
foundingClub
Indicates that one entity is a club that participated as a founding member in the creation or establishment of another entity (such as a league, organization, or competition).
-
E.
teamFoundedAs
Indicates the original name or identity under which a team was first established or created.
- 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_69f76e7011dc819082b324f18b756a1b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ff27b125948190aced0fe0189fd39a |
completed | May 9, 2026, 12:25 p.m. |
| PD | Predicate disambiguation | batch_69ff26c30a0481909ef6a54ded851e42 |
completed | May 9, 2026, 12:21 p.m. |
| PDg | Predicate description generation | batch_69ff27b0385c8190bccf340d26268f77 |
completed | May 9, 2026, 12:25 p.m. |
Created at: May 3, 2026, 4:12 p.m.