Triple
T17203664
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bruno Costa |
E417542
|
entity |
| Predicate | coFoundedInYear |
P126390
|
FINISHED |
| Object | 1971 |
—
|
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: 1971 | Statement: [Bruno Costa, coFoundedInYear, 1971]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coFoundedInYear Context triple: [Bruno Costa, coFoundedInYear, 1971]
-
A.
foundedAt
Indicates the time or date at which an entity (such as an organization, project, or institution) was established or created.
-
B.
foundedInYearApprox
Indicates that an entity was established or came into existence around an approximate year, rather than on a precisely known date.
-
C.
isFoundedOn
Indicates that one entity is established, created, or based upon another entity as its foundational source or principle.
-
D.
organizationTypeFounded
Indicates the type or category of organization that was established or created in a founding event.
-
E.
foundationFoundedIn
Indicates that a foundation was established or came into existence in a specific year or time period.
- 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_69d886d6ba8c819093215917b3d01689 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42db11fc881908291bf29cc740e09 |
completed | April 19, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69e3831e354881908c5505ffd15c84e9 |
completed | April 18, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69e3873f62108190966c4e741ebd548d |
completed | April 18, 2026, 1:29 p.m. |
Created at: April 10, 2026, 5:38 a.m.