Triple
T17601572
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crookston |
E428712
|
entity |
| Predicate | castleBuiltAround |
P44105
|
FINISHED |
| Object | 15th 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: 15th century | Statement: [Crookston, castleBuiltAround, 15th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: castleBuiltAround Context triple: [Crookston, castleBuiltAround, 15th century]
-
A.
castleBuilt
Indicates that a castle has been constructed or established, typically by a specific agent or during a particular time period.
-
B.
castleBuiltFor
Indicates that a castle was constructed specifically for the benefit, use, or commission of a particular person, group, or purpose.
-
C.
castleBuiltOf
Indicates that a castle is constructed primarily from a specified material.
-
D.
originalCastleFoundedIn
chosen
Indicates the specific year or time period when the original version of a castle was first established or built.
-
E.
fortressOriginallyBuiltBy
Indicates that a particular fortress was initially constructed by a specified builder or group.
- 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_69d889e1c6148190ba76241e74688f8b |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46c48dfc08190ba360e6082cffa87 |
completed | April 19, 2026, 5:46 a.m. |
| PD | Predicate disambiguation | batch_69e3b500c924819087c7107f86970675 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:51 a.m.