Triple
T14232615
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boeren |
E352788
|
entity |
| Predicate | associatedWithFoundingClubYear |
P39975
|
FINISHED |
| Object | 1913 |
—
|
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: 1913 | Statement: [Boeren, associatedWithFoundingClubYear, 1913]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithFoundingClubYear Context triple: [Boeren, associatedWithFoundingClubYear, 1913]
-
A.
associatedClubFounded
chosen
Indicates that there exists a club associated with an entity and specifies the date or time at which that associated club was founded.
-
B.
foundedAsClubInYear
Indicates that an organization was originally established as a club in the specified year.
-
C.
associationFoundedYear
Indicates the year in which an association was formally established or founded.
-
D.
associatedWithFormerClubName
Indicates a relationship where an entity is linked to the previous or former name of a club.
-
E.
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).
- 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_69d8278adc7c8190a9218d69bce3c4e6 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de622cdd6481908befa179a9675bb5 |
completed | April 14, 2026, 3:50 p.m. |
| PD | Predicate disambiguation | batch_69de05bf069c8190b69f00f00f5eb126 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 1:07 a.m.