Triple
T29751379
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lighthouse of Colonia del Sacramento |
E752908
|
entity |
| Predicate | builtOnRuinsOf |
P144184
|
FINISHED |
| Object | Convent of San Francisco |
—
|
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: Convent of San Francisco | Statement: [Lighthouse of Colonia del Sacramento, builtOnRuinsOf, Convent of San Francisco]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: builtOnRuinsOf Context triple: [Lighthouse of Colonia del Sacramento, builtOnRuinsOf, Convent of San Francisco]
-
A.
hasRuinsOn
Indicates that one location or object contains or is the site of ruins situated upon it.
-
B.
cityRuinsOf
Indicates that a city is located on or associated with the ruins of another, earlier city.
-
C.
rebuiltOnSiteOf
chosen
Indicates that a structure was reconstructed or newly built on the same physical location where an earlier structure once stood.
-
D.
builtOn
Indicates that one entity is constructed, developed, or established using another entity as its base, foundation, or underlying platform.
-
E.
rebuiltAsPalace
Indicates that a structure or building was reconstructed or transformed into a palace.
- 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_69f0d62c84cc8190846f80ae04fdf8ec |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f6736ad5e48190bab89c27970a8e74 |
completed | May 2, 2026, 9:58 p.m. |
| PD | Predicate disambiguation | batch_69f66ac1a4fc81909740d2e52fbe6970 |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 28, 2026, 7:54 p.m.