Triple
T38366172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Esporte Clube Vitória |
E892447
|
entity |
| Predicate | stateOfFoundation |
P199280
|
FINISHED |
| Object | Bahia |
—
|
NE NERFINISHED |
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: Bahia | Statement: [Esporte Clube Vitória, stateOfFoundation, Bahia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stateOfFoundation Context triple: [Esporte Clube Vitória, stateOfFoundation, Bahia]
-
A.
stateTypeFounded
Indicates that a particular type or category of state was established or came into existence at a certain point or by a certain founding event.
-
B.
stateFoundedIn
Indicates that a particular state was established or came into existence in a specified year or time period.
-
C.
foundingStatus
Indicates the relationship describing an entity’s role or condition in the creation or establishment of another entity (e.g., whether it is a founder, co-founder, or non-founder).
-
D.
stateFounded
Indicates that a particular state was established or created at a specific time or by a specific founding event or agent.
-
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_69f76e47cb4c8190bdd92cd1db59c0c5 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff29d831b881908d485609e0fc1d0b |
completed | May 9, 2026, 12:34 p.m. |
| PD | Predicate disambiguation | batch_69ff28f9f9e4819087f3402735de66c7 |
completed | May 9, 2026, 12:30 p.m. |
| PDg | Predicate description generation | batch_69ff29d77f48819085304ed5e92eb906 |
completed | May 9, 2026, 12:34 p.m. |
Created at: May 3, 2026, 4:31 p.m.