Triple
T1727669
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clare Bridge |
E37534
|
entity |
| Predicate | oldest |
P7751
|
FINISHED |
| Object | oldest surviving bridge in Cambridge |
—
|
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: oldest surviving bridge in Cambridge | Statement: [Clare Bridge, oldest, oldest surviving bridge in Cambridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oldest Context triple: [Clare Bridge, oldest, oldest surviving bridge in Cambridge]
-
A.
isOldest
chosen
Indicates that one entity has a greater age than all other relevant entities in the comparison set.
-
B.
isOldestOrderOf
Indicates that one order is the earliest or first created among a set of related orders for a given context or entity.
-
C.
oldestKnownFeature
Indicates that the related feature is the earliest or most ancient one known within a given context or set.
-
D.
isOldestCityIn
Indicates that one city holds the distinction of being the most ancient or earliest established within a specified region, country, or group of cities.
-
E.
ancestor
Indicates that one entity is a forebear of another in a lineage, occurring in an earlier generation and connected through one or more parent-child relationships.
- 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_69a8861acab88190bb43cde203429399 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aadb7bda1081908f2c41c520c9c55c |
completed | March 6, 2026, 1:49 p.m. |
| PD | Predicate disambiguation | batch_69aa61c0a0288190bce9d60062a84b69 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:30 p.m.