Triple
T35310210
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Os Celestes |
E1019748
|
entity |
| Predicate | appliesToClubFoundedIn |
P102441
|
FINISHED |
| Object | 1923 |
—
|
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: 1923 | Statement: [Os Celestes, appliesToClubFoundedIn, 1923]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesToClubFoundedIn Context triple: [Os Celestes, appliesToClubFoundedIn, 1923]
-
A.
supportsClubFoundedIn
Indicates that an entity provides backing or endorsement to a club that was established in a specific year or time period.
-
B.
appliesToClub
chosen
Indicates that something (such as a rule, policy, attribute, or action) is relevant or applicable specifically to a particular club.
-
C.
associatedClubFounded
Indicates that there exists a club associated with an entity and specifies the date or time at which that associated club was founded.
-
D.
foundedClub
Indicates that an entity established or created a club.
-
E.
appliedToFranchiseFoundedIn
Indicates that something (such as a rule, policy, or action) is applied specifically to a franchise that was founded in a particular time or place.
- 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_69f76de8b4c48190ae504b86185c474c |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff3e1762d8819089a60e402e682817 |
completed | May 9, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69ff3d8c6f308190a0646b1432752eb8 |
completed | May 9, 2026, 1:58 p.m. |
Created at: May 3, 2026, 4:03 p.m.