Triple
T34720522
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | trio elétrico |
E1000899
|
entity |
| Predicate | notableStateOfUse |
P18999
|
FINISHED |
| Object | Bahia |
E199233
|
NE 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: Bahia | Statement: [trio elétrico, notableStateOfUse, Bahia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableStateOfUse Context triple: [trio elétrico, notableStateOfUse, Bahia]
-
A.
notableUse
Indicates that something is prominently or famously used by a particular entity, context, or for a specific purpose.
-
B.
notableUseCountry
Indicates that something is notably or prominently used within a particular country.
-
C.
notableState
chosen
Indicates that an entity is significantly associated with, recognized in, or prominently linked to a particular state (such as a U.S. state or similar regional jurisdiction).
-
D.
notableLocationUse
Indicates that a location is notably used for a particular purpose, activity, or function associated with the subject.
-
E.
notableUseEvent
Indicates an event in which something is used in a way that is significant or noteworthy, distinguishing it from ordinary or routine use.
- F. None of above.
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_69f76dad3f108190a280fd0a2f4ee89a |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a375bdce1a081909d549684fb6e55a8 |
completed | June 21, 2026, 3:34 a.m. |
| PD | Predicate disambiguation | batch_6a0379fd7aac8190873077e63873aa72 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 3:59 p.m.