Triple
T24963401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Praia de Maceió |
E624670
|
entity |
| Predicate | temCenario |
P107448
|
FINISHED |
| Object | vilas de pescadores |
—
|
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: vilas de pescadores | Statement: [Praia de Maceió, temCenario, vilas de pescadores]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: temCenario Context triple: [Praia de Maceió, temCenario, vilas de pescadores]
-
A.
scenarioType
Indicates the specific category or kind of situation, context, or use case that an entity or event is associated with.
-
B.
scenes
chosen
Indicates that one entity is a scene or setting in which the other entity occurs, appears, or is depicted.
-
C.
variantScenario
Indicates a scenario that represents an alternative, modified, or derived version of another base scenario.
-
D.
snapSituation
Indicates a situation or context in which a sudden, decisive, or snapshot-like event or state occurs between entities.
-
E.
stageEnvironment
Indicates that an entity is placed into or operates within a non-production (staging) environment used for testing or pre-deployment.
- 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.