Triple
T20848998
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grace Cathedral, San Francisco |
E513302
|
entity |
| Predicate | hasInteriorLabyrinth |
P6655
|
FINISHED |
| Object | indoor labyrinth |
—
|
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: indoor labyrinth | Statement: [Grace Cathedral, San Francisco, hasInteriorLabyrinth, indoor labyrinth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInteriorLabyrinth Context triple: [Grace Cathedral, San Francisco, hasInteriorLabyrinth, indoor labyrinth]
-
A.
hasInteriorFeature
chosen
Indicates that an entity contains or includes a specific feature within its interior space.
-
B.
hasBodyCavity
Indicates that an organism possesses an internal body cavity or space within its body structure.
-
C.
hasMantleCavity
Indicates that an organism possesses a mantle cavity, a body space formed by the mantle that typically houses gills, excretory openings, and other organs.
-
D.
locatedInTheInteriorOf
Indicates that one entity is situated entirely within the inner part or inside area of another entity, rather than on its surface or boundary.
-
E.
hasCaves
Indicates that one entity possesses, contains, or is characterized by the presence of caves.
- 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_69e0b4f4898081908209e58edb8f9c45 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c3520b0081908ce0f43e8f20b24c |
completed | April 21, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a593f481908beb457c29f1ce73 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:43 p.m.