Triple
T24950307
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poemas de Pernambuco |
E624311
|
entity |
| Predicate | hasRegionDepicted |
P146643
|
FINISHED |
| Object | Recife |
—
|
NE NERFINISHED |
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: Recife | Statement: [Poemas de Pernambuco, hasRegionDepicted, Recife]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRegionDepicted Context triple: [Poemas de Pernambuco, hasRegionDepicted, Recife]
-
A.
primaryRegionDepicted
Indicates that a resource primarily depicts or visually represents a particular geographic or spatial region as its main subject.
-
B.
hasRegion
Indicates that an entity includes, contains, or is associated with a specific geographic or administrative region as part of its scope or structure.
-
C.
portrayalRegion
chosen
Indicates the geographic or spatial area in which something is depicted, represented, or portrayed.
-
D.
mentionsRegion
Indicates that one entity explicitly refers to or cites a specific geographic region in its content or context.
-
E.
isRegion
Indicates that one entity functions as a geographic or administrative region associated with another entity.
- 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_69e2ff22e4c48190a0444b5a044f14e8 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f67c9fe7b48190b79b4041357edb49 |
completed | May 2, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69f678cc272081909e5c70f1bc7407f0 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 18, 2026, 5:56 a.m.