Triple
T37500071
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oudenbosch |
E931932
|
entity |
| Predicate | basilicaModeledAfter |
P188403
|
FINISHED |
| Object | St. Peter's Basilica |
—
|
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: St. Peter's Basilica | Statement: [Oudenbosch, basilicaModeledAfter, St. Peter's Basilica]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basilicaModeledAfter Context triple: [Oudenbosch, basilicaModeledAfter, St. Peter's Basilica]
-
A.
basilicaStyle
Indicates that something is designed, built, or characterized in the architectural style of a basilica.
-
B.
basilicaHeightApprox
Indicates that an entity is approximately a certain height, specifically in the context of a basilica or basilica-like structure.
-
C.
hasBasilica
Indicates that one entity possesses, contains, or is associated with a basilica as a significant feature or component.
-
D.
basilicaFunction
Indicates that one entity serves as the functional role, purpose, or use of a basilica in relation to another entity.
-
E.
basilicaDate
Indicates the date associated with a basilica, such as its construction, consecration, or official designation.
- 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_69f76ec5268481909ea01c73aeeefd42 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba68077788190b311e027435fcf87 |
completed | May 6, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fba34c65ac8190b298f0f00d1dcc0e |
completed | May 6, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69fba67f78348190ab160988e4698394 |
completed | May 6, 2026, 8:37 p.m. |
Created at: May 3, 2026, 4:17 p.m.