Triple
T1137655
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mission San Diego de Alcalá |
E23175
|
entity |
| Predicate | hasBelltower |
P2495
|
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: [Mission San Diego de Alcalá, hasBelltower, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBelltower Context triple: [Mission San Diego de Alcalá, hasBelltower, yes]
-
A.
hasBellTower
chosen
Indicates that one entity (typically a building or structure) possesses or includes a bell tower as part of it.
-
B.
hasTower
Indicates that one entity possesses, contains, or is characterized by the presence of a tower.
-
C.
hasClockTower
Indicates that one entity possesses or features a clock tower as part of its structure or property.
-
D.
hasTowerHeight
Indicates that an entity (such as a tower or structure) has a specific height value associated with it.
-
E.
hasBells
Indicates that an entity possesses or is equipped with one or more bells.
- 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_69a493ec75988190b63a11bafaec29b4 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4bde18d208190848c189b2b8d585f |
completed | March 1, 2026, 10:29 p.m. |
| PD | Predicate disambiguation | batch_69a4bb4b52d48190bec2e7ad1cc8efc0 |
completed | March 1, 2026, 10:18 p.m. |
Created at: March 1, 2026, 7:44 p.m.