Triple
T25071391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clark Bridge |
E627919
|
entity |
| Predicate | isRegionalLandmark |
P157609
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Clark Bridge, isRegionalLandmark, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRegionalLandmark Context triple: [Clark Bridge, isRegionalLandmark, true]
-
A.
isLandmarkFor
Indicates that one entity serves as a notable or significant reference point or attraction for another entity, such as a place, route, or area.
-
B.
isUrbanLandmark
Indicates that a place or structure is recognized as a notable or significant landmark within an urban environment.
-
C.
isSocialLandmark
Indicates that a place functions as a notable social gathering point or reference location within a community or area.
-
D.
hasTouristAttractionRole
Indicates that an entity serves in the capacity or function of a tourist attraction for another entity (such as a place, organization, or area).
-
E.
isLocalLandmark
Indicates that something is recognized as a notable or significant landmark within a specific local area or community.
- 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_69e2ff2d71dc8190b4758e57d643cbe4 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f45d14c8a8819093a0cea7bcf56400 |
completed | May 1, 2026, 7:58 a.m. |
| PD | Predicate disambiguation | batch_69f442c861188190967655c6d8012380 |
completed | May 1, 2026, 6:06 a.m. |
| PDg | Predicate description generation | batch_69f448fe11f08190bdd53ca7ba2d51e4 |
completed | May 1, 2026, 6:32 a.m. |
Created at: April 18, 2026, 6:10 a.m.