Triple
T24387439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trinity Bridge |
E614785
|
entity |
| Predicate | townFeature |
P46334
|
FINISHED |
| Object | landmark of Crowland |
—
|
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: landmark of Crowland | Statement: [Trinity Bridge, townFeature, landmark of Crowland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: townFeature Context triple: [Trinity Bridge, townFeature, landmark of Crowland]
-
A.
notableLocationFeature
chosen
Indicates that a location is characterized or distinguished by a particular notable physical or contextual feature.
-
B.
tourismFeature
Indicates that something serves as an attraction, amenity, or point of interest relevant to tourism or visitors.
-
C.
hostCityFeature
Indicates that a particular feature, attribute, or characteristic is associated with or present in a host city.
-
D.
refersToUrbanFeature
Indicates that one entity makes reference or points specifically to an urban feature such as a city-related structure, space, or infrastructure element.
-
E.
cityFunction
Indicates the primary role, purpose, or functional classification associated with a city (e.g., administrative, commercial, industrial, cultural).
- 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_69e2d7e362e481909e32fe4ef8269d4f |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f29455e7fc8190841f909b970f6bd3 |
completed | April 29, 2026, 11:29 p.m. |
| PD | Predicate disambiguation | batch_69f287c4a2b48190b80fb7a3c0e9b018 |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:03 a.m.