Triple
T8942028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Balsham |
E212924
|
entity |
| Predicate | hasHistoricFeatures |
P86463
|
FINISHED |
| Object | medieval parish church |
—
|
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: medieval parish church | Statement: [Balsham, hasHistoricFeatures, medieval parish church]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricFeatures Context triple: [Balsham, hasHistoricFeatures, medieval parish church]
-
A.
hasHistoricalData
Indicates that an entity possesses recorded information or records about past events, states, or values relevant to it.
-
B.
hasHistoricMarker
Indicates that something is associated with or identified by an official historic marker or plaque recognizing its historical significance.
-
C.
hasHistoricalEntity
Indicates a relationship where one entity includes, references, or is associated with another entity that existed or is defined in a past historical context.
-
D.
hasHistoricalCategory
Indicates that something is associated with a particular historical classification, period, or type based on its past context or significance.
-
E.
hasFlagHistory
Indicates that there exists a historical record or sequence of changes related to an entity’s flag.
- 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_69ca839694c88190b324ffeb43d23b08 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc66b9c14c8190b80c3df0cdba2747 |
completed | April 1, 2026, 12:28 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed5267c8190a43feb2a2f3df1ec |
completed | March 31, 2026, 11:55 p.m. |
| PDg | Predicate description generation | batch_69cc60e0d7208190966797ce5f95fe49 |
completed | April 1, 2026, 12:03 a.m. |
Created at: March 30, 2026, 6:58 p.m.