Triple
T14589494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Herstmonceux, East Sussex |
E342405
|
entity |
| Predicate | observatoryOperationalPeriod |
P114967
|
FINISHED |
| Object | mid-20th 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: mid-20th century | Statement: [Herstmonceux, East Sussex, observatoryOperationalPeriod, mid-20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: observatoryOperationalPeriod Context triple: [Herstmonceux, East Sussex, observatoryOperationalPeriod, mid-20th century]
-
A.
observatoryOpened
Indicates that an observatory has begun operating or has been officially opened for use.
-
B.
observatoryOperator
Indicates that one entity operates, manages, or runs an observatory facility for another entity or in an official capacity.
-
C.
observatoryConstructionStart
Indicates the date or event marking when construction of an observatory begins.
-
D.
observationalVisibility
Indicates that one entity is able to observe or visually perceive another entity under given conditions.
-
E.
observatoryType
Indicates the specific kind or category of observatory associated with an entity.
- 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_69d822ddc0f081909cd8163c7de298cd |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb4237d88819097f3f9a40f5be152 |
completed | April 14, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69de656a953481909a4645b004c40de7 |
completed | April 14, 2026, 4:03 p.m. |
| PDg | Predicate description generation | batch_69de716c17cc8190aeb85296abee85a7 |
completed | April 14, 2026, 4:55 p.m. |
Created at: April 10, 2026, 1:24 a.m.