Triple
T34938626
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Robert (Cathedral) |
E1007650
|
entity |
| Predicate | originOfVisit |
P74830
|
FINISHED |
| Object | Connecticut |
E10549
|
NE 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: Connecticut | Statement: [Robert (Cathedral), originOfVisit, Connecticut]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originOfVisit Context triple: [Robert (Cathedral), originOfVisit, Connecticut]
-
A.
originSite
Indicates the place or site from which something or someone originally comes or is derived.
-
B.
typicalVisitorOrigin
chosen
Indicates the usual geographic source or location from which visitors to a place, event, or entity most commonly come.
-
C.
registrationOrigin
Indicates the source or context from which a registration event was initiated or created.
-
D.
tourOrigin
Indicates the place from which a tour or journey starts or is initiated.
-
E.
wasFirstVisitedBy
Indicates that a particular entity was initially reached, discovered, or visited by another specified entity before any others.
- F. None of above.
Provenance (4 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_69f76dc513fc819084a1ff52abbfa5bc |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a37bd05043881909a4e80ceb7ad575c |
completed | June 21, 2026, 10:29 a.m. |
| PD | Predicate disambiguation | batch_6a0379ff1ba081908eda86acefcf69fb |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4 p.m.