Triple
T10788349
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St Mary Cray |
E254505
|
entity |
| Predicate | historicCore |
P95486
|
FINISHED |
| Object | village core |
—
|
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: village core | Statement: [St Mary Cray, historicCore, village core]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicCore Context triple: [St Mary Cray, historicCore, village core]
-
A.
historicFor
Indicates that something holds historical significance or importance specifically in relation to another entity.
-
B.
historicActivity
Indicates that an entity engaged in an activity or event of historical significance in the past.
-
C.
historicalStructure
Indicates that the subject is a structure recognized for its historical significance or heritage value.
-
D.
historicallyRich
Indicates that an entity possesses significant historical depth, importance, or a wealth of notable past events and heritage.
-
E.
otherHistoricSee
Indicates that an entity is associated with or linked to another historically significant site, event, or point of interest that can be seen or visited.
- 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_69d6aa609f008190a294200aefcb7bd5 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d732d65fcc8190ab5573a861409c56 |
completed | April 9, 2026, 5:02 a.m. |
| PD | Predicate disambiguation | batch_69d6f316940c819092a96c429629fdef |
completed | April 9, 2026, 12:30 a.m. |
| PDg | Predicate description generation | batch_69d6fa334b8c819082eaf8537084c323 |
completed | April 9, 2026, 1 a.m. |
Created at: April 8, 2026, 9:17 p.m.