Triple
T24963406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Praia de Maceió |
E624670
|
entity |
| Predicate | acessoPrincipal |
P144828
|
FINISHED |
| Object | rodoviário |
—
|
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: rodoviário | Statement: [Praia de Maceió, acessoPrincipal, rodoviário]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: acessoPrincipal Context triple: [Praia de Maceió, acessoPrincipal, rodoviário]
-
A.
mainAccessFor
chosen
Indicates that one entity serves as the primary means or route of access for another entity.
-
B.
accessPrinciple
Indicates that one entity has the right, ability, or method to obtain, use, or interact with another entity or resource under defined conditions.
-
C.
canAccedeTo
Indicates that one entity has the ability, permission, or right to gain access to or enter into another entity, resource, or state.
-
D.
accessIs
Indicates that one entity has the ability, permission, or means to reach, use, or interact with another entity or resource.
-
E.
accessRole
Indicates the specific permissions or level of authority an entity has when accessing another entity or resource.
- 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_69e2ff23a3a88190b1b9743fe5e15f94 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f4242f0968819098c3f0f92054d22f |
completed | May 1, 2026, 3:55 a.m. |
| PD | Predicate disambiguation | batch_69f4210130d08190ae30b7943f7a0bbc |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 5:59 a.m.