Triple
T27162948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carlow Courthouse |
E682708
|
entity |
| Predicate | architectKnownFor |
P42691
|
FINISHED |
| Object | James Gandon |
—
|
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: James Gandon | Statement: [Carlow Courthouse, architectKnownFor, James Gandon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: architectKnownFor Context triple: [Carlow Courthouse, architectKnownFor, James Gandon]
-
A.
architectIsNotableFor
Indicates that an architect is recognized or distinguished for a particular work, contribution, or achievement.
-
B.
coArchitectOf
Indicates a relationship where two or more entities jointly serve as architects of the same project, design, or structure.
-
C.
architectOfStructure
Indicates that an entity is the designer or creator responsible for the architectural design of a particular structure.
-
D.
hasLandmarkArchitect
chosen
Indicates that a landmark is associated with, or was designed by, a specific architect.
-
E.
architecturalContribution
Indicates a relationship where an entity contributes to the design, planning, or creation of an architectural work or feature.
- 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_69eefacf6e788190a75a64399d9e3109 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f6a28c7c148190bfc980aad9f678ca |
completed | May 3, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69f69fe1e3c88190830bb2e9f407357e |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 27, 2026, 9:19 a.m.