Triple
T9668513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holme-next-the-Sea |
E233766
|
entity |
| Predicate | seahengeDiscovered |
P89508
|
FINISHED |
| Object | 1998 |
—
|
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: 1998 | Statement: [Holme-next-the-Sea, seahengeDiscovered, 1998]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seahengeDiscovered Context triple: [Holme-next-the-Sea, seahengeDiscovered, 1998]
-
A.
MIThengePhenomenon
Indicates the occurrence of the specific alignment phenomenon at MIT where the sun’s position creates a notable visual effect along a campus axis or structure.
-
B.
discoveredInAntiquity
Indicates that something was found, identified, or recognized during ancient historical times rather than in the modern era.
-
C.
hasArchaeologicalSitesFrom
Indicates that an entity contains or is associated with archaeological sites dating from a specified time period or era.
-
D.
excavatedAt
Indicates that an excavation activity took place at a specific location or site.
-
E.
excavatedIn
Indicates that something (typically an artifact, structure, or site) was uncovered or dug out during an excavation that took place at a specific time or within a specific time period.
- 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_69ca848d3b6c8190ae98ea554dea58df |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9c3d5b3481908c8c66a3528875aa |
completed | April 1, 2026, 10:29 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b3239c8190b3ae3b9bd121e4bd |
completed | April 1, 2026, 8:22 a.m. |
| PDg | Predicate description generation | batch_69ccd9408c848190b84dd74d87f76273 |
completed | April 1, 2026, 8:37 a.m. |
Created at: March 30, 2026, 8:15 p.m.