Triple
T15874660
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St. Mary’s Church, Orange |
E384921
|
entity |
| Predicate | architectOrigin |
P120864
|
FINISHED |
| Object | Los Angeles-based architect |
—
|
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: Los Angeles-based architect | Statement: [St. Mary’s Church, Orange, architectOrigin, Los Angeles-based architect]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: architectOrigin Context triple: [St. Mary’s Church, Orange, architectOrigin, Los Angeles-based architect]
-
A.
architecturalOrigin
Indicates the place, style, or tradition from which an architectural work or design originates.
-
B.
buildingArchitectOfOriginal
Indicates that an entity is the architect responsible for the original design of a particular building.
-
C.
coArchitectOf
Indicates a relationship where two or more entities jointly serve as architects of the same project, design, or structure.
-
D.
earlierArchitect
Indicates that one architect’s work, involvement, or role occurred before that of another architect in time.
-
E.
architectNationality
Indicates the country or national affiliation associated with an architect.
- F. None of above. chosen
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_69d86da4e86481909f1325fdc971b5ec |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e174de2cd48190ab18e48c9f051a2a |
completed | April 16, 2026, 11:46 p.m. |
| PD | Predicate disambiguation | batch_69e142c3e18c8190bb7b023f4a0eaebb |
completed | April 16, 2026, 8:12 p.m. |
| PDg | Predicate description generation | batch_69e174da2c2c819099ec46616798245a |
completed | April 16, 2026, 11:46 p.m. |
Created at: April 10, 2026, 4:51 a.m.