Triple
T36233869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Acomb |
E891322
|
entity |
| Predicate | hasHistoricSurroundings |
P199846
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Acomb, hasHistoricSurroundings, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricSurroundings Context triple: [Acomb, hasHistoricSurroundings, true]
-
A.
hasLocalHistoricalAssociations
Indicates that something is connected to historically significant events, people, or developments specific to a particular locality or region.
-
B.
hasHistoricSite
Indicates that an entity possesses, contains, or is associated with a place recognized for its historical significance.
-
C.
hasHistoricPremises
Indicates that an entity possesses or is associated with premises that have historical significance or heritage value.
-
D.
hasHistoricSignificanceFor
Indicates that something holds notable historical importance or relevance for a particular entity or group.
-
E.
hasHistoricalSignificanceThrough
Indicates that one entity possesses historical importance or relevance by means of, or as established through, its connection or association with another entity or event.
- 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_69f76e4387048190a1b27bcbf4ec7423 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff5b233e9c8190adc06cca0758986b |
completed | May 9, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69ff5a5682108190a006b23c4fcdcc7c |
completed | May 9, 2026, 4:01 p.m. |
| PDg | Predicate description generation | batch_69ff5b224b8c8190bd0955876098ecc8 |
completed | May 9, 2026, 4:04 p.m. |
Created at: May 3, 2026, 4:09 p.m.