Triple
T10905343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Esporte Clube Bahia |
E257553
|
entity |
| Predicate | hasHistoricTitles |
P96339
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Esporte Clube Bahia, hasHistoricTitles, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricTitles Context triple: [Esporte Clube Bahia, hasHistoricTitles, yes]
-
A.
hasTitleSince
Indicates that an entity has held a particular title continuously starting from a specified point in time.
-
B.
hasHistoricNickname
Indicates that an entity is known by a nickname that has historical significance or longstanding traditional use.
-
C.
hasHistoricalText
Indicates that an entity is associated with a historical written document or record describing it or its past.
-
D.
isHistoric
Indicates that something has significant importance or relevance in history, often due to its age, impact, or role in past events.
-
E.
hasHistoricMarker
Indicates that something is associated with or identified by an official historic marker or plaque recognizing its historical significance.
- 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_69d6aa8550c8819095508a2ed9acf3db |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d770656c288190828e71600bb0acd4 |
completed | April 9, 2026, 9:24 a.m. |
| PD | Predicate disambiguation | batch_69d70d3d69e08190bb369e9a7927142c |
completed | April 9, 2026, 2:21 a.m. |
| PDg | Predicate description generation | batch_69d7101de31c819090707635f6790559 |
completed | April 9, 2026, 2:34 a.m. |
Created at: April 8, 2026, 9:22 p.m.