Triple
T36545641
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Bridge of Stonebows |
E901132
|
entity |
| Predicate | typeOfCrossing |
P10712
|
FINISHED |
| Object | stone bridge |
—
|
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: stone bridge | Statement: [The Bridge of Stonebows, typeOfCrossing, stone bridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfCrossing Context triple: [The Bridge of Stonebows, typeOfCrossing, stone bridge]
-
A.
crossingType
chosen
Indicates the specific kind or category of crossing (e.g., how or where one thing passes over, through, or across another).
-
B.
crossingOf
Indicates that one entity serves as the intersection or crossing point of two or more linear features, such as roads, paths, or tracks.
-
C.
crossingStyle
Indicates the manner or method by which one entity crosses or traverses another (such as a boundary, path, or medium).
-
D.
crossingStructure
Indicates that one entity serves as a structure enabling passage across or over another entity, such as a bridge, tunnel, or overpass.
-
E.
crossType
Indicates a relationship where one entity intersects, passes over, or traverses another, typically implying movement or extension across a boundary, area, or medium.
- 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_69f76e61217081908b79d610fe67b013 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a0314e613f88190b5dbf89b9c4203c6 |
completed | May 12, 2026, 11:54 a.m. |
| PD | Predicate disambiguation | batch_6a0314699c1c8190b2a80dc4015e7890 |
completed | May 12, 2026, 11:52 a.m. |
Created at: May 3, 2026, 4:11 p.m.