Triple
T11103948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tiberius Bridge |
E262578
|
entity |
| Predicate | hasPiers |
P15921
|
FINISHED |
| Object | massive stone piers |
—
|
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: massive stone piers | Statement: [Tiberius Bridge, hasPiers, massive stone piers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPiers Context triple: [Tiberius Bridge, hasPiers, massive stone piers]
-
A.
hasPiersOn
Indicates that one structure or location is supported or extended by piers that are physically situated on another structure or surface.
-
B.
hasPier
chosen
Indicates that a location or structure possesses or includes a pier as part of its features.
-
C.
hasPierFunction
Indicates that an entity serves the role or function of a pier, such as providing a structure that extends over water for access, docking, or related activities.
-
D.
hasPierLength
Indicates that one entity (typically a pier or similar structure) has a specified length measurement.
-
E.
hasNumberOfPiersInWater
Indicates the quantity of piers that extend into or are situated within a body of water.
- 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_69d6aa9a40d88190a373e2c7e48285db |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d79a2d33948190ac29d174694a78e5 |
completed | April 9, 2026, 12:23 p.m. |
| PD | Predicate disambiguation | batch_69d7441aa3548190b92dbde57841c135 |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:27 p.m.