Triple
T23666875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nossa Senhora de Lourdes |
E584602
|
entity |
| Predicate | locatedInInteriorRegion |
P109650
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Nossa Senhora de Lourdes, locatedInInteriorRegion, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInInteriorRegion Context triple: [Nossa Senhora de Lourdes, locatedInInteriorRegion, true]
-
A.
locatedInTheInteriorOf
chosen
Indicates that one entity is situated entirely within the inner part or inside area of another entity, rather than on its surface or boundary.
-
B.
locatedInland
Indicates that something is situated away from the coast or shoreline, within the interior of a land area.
-
C.
sometimesLocatedIn
Indicates that an entity is located in a given place only at certain times or under certain conditions, rather than permanently or always.
-
D.
locatedIn
Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of another entity.
-
E.
hasInteriorFeature
Indicates that an entity contains or includes a specific feature within its interior space.
- 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_69e24901421881908c17a5293bdd4a8e |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b40c48088190a61e9a73919bace5 |
completed | April 29, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69f118dd13008190a8799b4e9cadbd79 |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:50 p.m.