Triple
T36597044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Osma Cathedral |
E902829
|
entity |
| Predicate | hasCloisterCourtyard |
P17704
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Osma Cathedral, hasCloisterCourtyard, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCloisterCourtyard Context triple: [Osma Cathedral, hasCloisterCourtyard, yes]
-
A.
hasCloister
chosen
Indicates that one entity possesses or includes a cloister as part of its structure or layout.
-
B.
hasCloisterWalls
Indicates that something possesses or is surrounded by cloister walls as an architectural feature.
-
C.
hasCourtyard
Indicates that one entity includes, features, or is characterized by the presence of a courtyard.
-
D.
hasCourtyardFeature
Indicates that a courtyard possesses or includes a specific feature or characteristic.
-
E.
hasCourtyardArea
Indicates that an entity includes or is associated with a courtyard and specifies the size or extent of that courtyard 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_69f76e66b7b88190848f7a3e1188915f |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fdb45537288190b6791078d4a6899f |
completed | May 8, 2026, 10 a.m. |
| PD | Predicate disambiguation | batch_69fdb39ad96481908376d7def9fafc13 |
completed | May 8, 2026, 9:57 a.m. |
Created at: May 3, 2026, 4:11 p.m.