Triple
T19014407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bishop of Trimythous |
E465307
|
entity |
| Predicate | seeCityType |
P134132
|
FINISHED |
| Object | ancient town |
—
|
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: ancient town | Statement: [Bishop of Trimythous, seeCityType, ancient town]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seeCityType Context triple: [Bishop of Trimythous, seeCityType, ancient town]
-
A.
cityView
Indicates that one entity offers a view of, or overlooks, a city.
-
B.
isUrbanSee
Indicates a relationship where a location or area is recognized or classified as an urban settlement or city-like environment.
-
C.
cityPanorama
Indicates a wide, comprehensive visual view or representation of a cityscape, typically encompassing many of its features in a single scene.
-
D.
seeType
Indicates that one entity observes, recognizes, or visually perceives another entity of a particular type or category.
-
E.
metropolitanSee
Indicates a relationship where one metropolitan area views, oversees, or conceptually regards another place, entity, or aspect within its sphere of influence.
- 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_69d8dd025c188190a1d81f5b4ec7e2c6 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d6d9f2a081908c0e923809da88e2 |
completed | April 20, 2026, 7:33 a.m. |
| PD | Predicate disambiguation | batch_69e4a2fd80c081908237317a3a883e1c |
completed | April 19, 2026, 9:40 a.m. |
| PDg | Predicate description generation | batch_69e4ad8e075c8190ad561edc5e520057 |
completed | April 19, 2026, 10:25 a.m. |
Created at: April 10, 2026, 12:02 p.m.