Triple
T29318508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St. Andrew’s Church, Dublin |
E743444
|
entity |
| Predicate | primaryEntranceFrom |
P106736
|
FINISHED |
| Object | Suffolk Street |
—
|
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: Suffolk Street | Statement: [St. Andrew’s Church, Dublin, primaryEntranceFrom, Suffolk Street]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryEntranceFrom Context triple: [St. Andrew’s Church, Dublin, primaryEntranceFrom, Suffolk Street]
-
A.
isMainEntrance
Indicates that an entrance serves as the primary or principal access point to a place or building.
-
B.
mainEntranceLocation
chosen
Indicates the location where the primary or main entrance of an entity is situated.
-
C.
isSecondaryEntranceOf
Indicates that one entrance serves as an additional or subordinate access point to a primary entrance of the same place or structure.
-
D.
hasEntranceOn
Indicates that one entity’s entrance or access point is located on or faces a specified side, boundary, or feature of another entity.
-
E.
primaryPortalOfEntry
Indicates the main route or location through which something (such as a substance, pathogen, or agent) first enters a host or system.
- 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_69f0912502c8819087d9e8398ee991a8 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_6a00dc330b148190aaae2ac6a5327960 |
completed | May 10, 2026, 7:27 p.m. |
| PD | Predicate disambiguation | batch_6a00d9d2904881909dafbfe7b9e5ad81 |
completed | May 10, 2026, 7:17 p.m. |
Created at: April 28, 2026, 1:21 p.m.