Triple
T7265337
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toon Army |
E159757
|
entity |
| Predicate | supportsClubFounded |
P62121
|
FINISHED |
| Object | 1892 |
—
|
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: 1892 | Statement: [Toon Army, supportsClubFounded, 1892]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsClubFounded Context triple: [Toon Army, supportsClubFounded, 1892]
-
A.
supportsClubFoundedIn
Indicates that an entity provides backing or endorsement to a club that was established in a specific year or time period.
-
B.
associatedClubFounded
Indicates that there exists a club associated with an entity and specifies the date or time at which that associated club was founded.
-
C.
clubFoundedSupported
chosen
Indicates that an entity (such as a person, organization, or group) played a role in founding a club and/or providing support for its establishment or ongoing activities.
-
D.
supportsClubInLeague
Indicates that one entity provides backing or sponsorship for a club participating in a particular league.
-
E.
supportsClubIdentity
Indicates that one entity actively upholds, reinforces, or contributes to maintaining the identity, values, or character of a club.
- 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_69c68838f9948190875fd60b2351230c |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6eb088dac8190b353f6ea3d686025 |
completed | March 27, 2026, 8:39 p.m. |
| PD | Predicate disambiguation | batch_69c6e76876608190ac4652bc7153302e |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 2:57 p.m.