Triple
T28311327
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Groote Schuur |
E714002
|
entity |
| Predicate | periodOfMajorRenovation |
P25681
|
FINISHED |
| Object | late 19th century |
—
|
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: late 19th century | Statement: [Groote Schuur, periodOfMajorRenovation, late 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: periodOfMajorRenovation Context triple: [Groote Schuur, periodOfMajorRenovation, late 19th century]
-
A.
renovationPeriod
chosen
Indicates the time span during which an object, structure, or entity undergoes renovation or refurbishment.
-
B.
renovatedAfter
Indicates that one entity was renovated at a later time than another entity.
-
C.
wasRenovatedFor
Indicates that an existing entity underwent renovation specifically to serve the needs, purposes, or use of another entity.
-
D.
renovationYear
Indicates the year in which an entity underwent renovation or significant refurbishment.
-
E.
renovatedBy
Indicates that an entity has been improved, restored, or updated through renovation work performed 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_69efb5256afc8190b9322d25c3ae6320 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f6617ba4a88190bfc5c305acb4f93f |
completed | May 2, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f660f082508190a95a7888ad66cb2e |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 27, 2026, 11:40 p.m.