Triple
T9948898
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MIN |
E195275
|
entity |
| Predicate | foundedForTeam |
P47177
|
FINISHED |
| Object | 1989 |
—
|
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: 1989 | Statement: [MIN, foundedForTeam, 1989]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundedForTeam Context triple: [MIN, foundedForTeam, 1989]
-
A.
foundedAsTeam
Indicates that an organization or club was originally established in the form of a team.
-
B.
foundedFor
Indicates that an entity was established or created specifically to serve, support, or benefit another entity or purpose.
-
C.
foundedAsRepresentativeTeam
chosen
Indicates that an entity was established specifically to serve as a representative team for a larger group, organization, or region.
-
D.
foundedWith
Indicates that an entity was established or created together with another entity, typically as co-founders or jointly initiated partners.
-
E.
foundedBySiblingTeam
Indicates that an entity (such as an organization, project, or venture) was established by a team composed of siblings working together as co-founders.
- 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_69ca82e96a108190932bd1fc4acd73a0 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb659307c81908279adb641ceef86 |
completed | April 2, 2026, 12:20 a.m. |
| PD | Predicate disambiguation | batch_69cd1d97c44081908730071269f07712 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:45 p.m.