Triple
T19493064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Freiburg Minster |
E487699
|
entity |
| Predicate | laterBuildingPhase |
P44772
|
FINISHED |
| Object | High Gothic period |
—
|
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: High Gothic period | Statement: [Freiburg Minster, laterBuildingPhase, High Gothic period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterBuildingPhase Context triple: [Freiburg Minster, laterBuildingPhase, High Gothic period]
-
A.
laterConstruction
Indicates that one construction event or structure occurred or was built after another in time.
-
B.
constructionPhase
chosen
Indicates the specific stage or period an entity is in within an overall construction or building process.
-
C.
processBuilding
Indicates the action of performing operations or transformations on a building or building-related data.
-
D.
laterBase
Indicates that one event, state, or version occurs or is valid at a later time than another referenced event, state, or version.
-
E.
laterBuiltOverBy
Indicates that a structure or feature was constructed at a later time on top of, or replacing, an earlier one.
- 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_69d8e8d9d1c88190b01cd78b8be49384 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6348f4d708190a6e612863fee4b97 |
completed | April 20, 2026, 2:13 p.m. |
| PD | Predicate disambiguation | batch_69e4fd7883308190b73912a71a35a835 |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:39 p.m.