Triple
T11408660
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lowestoft Lighthouse |
E270305
|
entity |
| Predicate | categoryOfListing |
P87
|
FINISHED |
| Object | Grade II |
—
|
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: Grade II | Statement: [Lowestoft Lighthouse, categoryOfListing, Grade II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: categoryOfListing Context triple: [Lowestoft Lighthouse, categoryOfListing, Grade II]
-
A.
categoryIUsedFor
Indicates that one entity is used as a category or classification label for another entity.
-
B.
category
chosen
Indicates that one entity is classified as a member or type within the grouping or class defined by another entity.
-
C.
apparentCategory
Indicates the category or type that something seems to belong to based on its observable characteristics, regardless of its true or underlying classification.
-
D.
subjectOfSale
Indicates that one entity is the item, asset, or right being transferred or offered in a sale transaction involving another entity.
-
E.
listingType
Indicates the category or format under which an item, property, or service is offered or advertised (e.g., for sale, for rent, auction, etc.).
- F. None of above.
Provenance (3 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_69d6aaddeaa8819088b30ef7b50598c9 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8014e72748190a01bde2f0105cedb |
completed | April 9, 2026, 7:43 p.m. |
| PD | Predicate disambiguation | batch_69d7e70ffd708190b62a78ebcbce9f78 |
completed | April 9, 2026, 5:51 p.m. |
Created at: April 8, 2026, 9:34 p.m.