Triple
T24425382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St. Bavochurch |
E615839
|
entity |
| Predicate | mainSquareContext |
P15345
|
FINISHED |
| Object | central square of Haarlem |
—
|
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: central square of Haarlem | Statement: [St. Bavochurch, mainSquareContext, central square of Haarlem]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainSquareContext Context triple: [St. Bavochurch, mainSquareContext, central square of Haarlem]
-
A.
mainSquare
chosen
Indicates that a location serves as the primary or central public square of a town or city.
-
B.
mainQuadrangle
Indicates that one location or structure serves as the primary central quadrangle area associated with another entity.
-
C.
mainReligiousBuildingOnSquare
Indicates that a religious building serves as the primary or most significant religious structure located on a particular square.
-
D.
capitalCitySquareOf
Indicates that one entity is a public square located in or associated with the capital city of the other entity.
-
E.
squareGivenBy
Indicates that one entity is a square (or square-shaped region) that has been specified, defined, or provided by another entity.
- 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_69e2d7eadb248190a867130fe45f0388 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f296a62644819089d01ec90e8bee3c |
completed | April 29, 2026, 11:39 p.m. |
| PD | Predicate disambiguation | batch_69f287cc4fd4819081e93cc638d9512d |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:15 a.m.