Triple
T24963393
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Praia de Maceió |
E624670
|
entity |
| Predicate | temVegetacao |
P949
|
FINISHED |
| Object | vegetação de restinga |
—
|
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: vegetação de restinga | Statement: [Praia de Maceió, temVegetacao, vegetação de restinga]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: temVegetacao Context triple: [Praia de Maceió, temVegetacao, vegetação de restinga]
-
A.
vegetationType
Indicates the specific kind or category of plant cover or flora that characterizes a given area or environment.
-
B.
vegetation
chosen
Indicates that an area or object is covered with, contains, or is characterized by plant life.
-
C.
vegetationCoverage
Indicates the extent or proportion of an area that is covered by vegetation.
-
D.
forestArea
Indicates the extent or size of land covered by forest within a given area or region.
-
E.
forestCoverCharacteristic
Indicates a relationship where a forested area possesses a specific attribute or quality related to its tree or vegetation cover.
- 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.