Triple
T25882924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teatro Nacional de Costa Rica |
E652100
|
entity |
| Predicate | capitalCityTheatreOf |
P83788
|
FINISHED |
| Object | San José |
—
|
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: San José | Statement: [Teatro Nacional de Costa Rica, capitalCityTheatreOf, San José]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capitalCityTheatreOf Context triple: [Teatro Nacional de Costa Rica, capitalCityTheatreOf, San José]
-
A.
countryCapitalTheatreOf
chosen
Indicates that a particular city serves as the main center or focal location for a country's theatrical or dramatic activities.
-
B.
municipalTheatre
Indicates that a theatre is designated, owned, or operated as a municipal (city- or town-run) institution.
-
C.
theatreCity
Indicates that a theatre is located in, or primarily associated with, a particular city.
-
D.
hasMunicipalTheatre
Indicates that a place or administrative entity possesses or contains a municipal theatre as one of its facilities.
-
E.
notableCityInTheater
Indicates that a city holds particular significance or prominence within a specified theater (such as a military, cultural, or operational region).
- 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_69e7ab3b92cc81908febd90317862647 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f638d11c988190af7fd4572b08e038 |
completed | May 2, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69f63706b6008190993577193c85ff50 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 22, 2026, 8:17 a.m.