Triple
T3236708
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Einstein–Rosen bridge |
E67871
|
entity |
| Predicate | traversability |
P13009
|
FINISHED |
| Object | non-traversable |
—
|
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: non-traversable | Statement: [Einstein–Rosen bridge, traversability, non-traversable]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traversability Context triple: [Einstein–Rosen bridge, traversability, non-traversable]
-
A.
navigability
chosen
Indicates how easily and effectively something (such as a space, interface, or route) can be traversed or moved through.
-
B.
terrainCapability
Indicates the types of terrain or ground conditions in which an entity can effectively operate or function.
-
C.
roadTraverses
Indicates that a road passes through, crosses, or extends across a specified geographic area or feature.
-
D.
isWalkable
Indicates that an entity can be traversed on foot, typically without obstruction or restriction.
-
E.
navigableFrom
Indicates that one location or entity can be reached or traversed from another, typically via a valid path, route, or connection.
- 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_69ad858d27348190abb61c280b4c86a9 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adaee05d34819095dbce4db6ac8613 |
completed | March 8, 2026, 5:16 p.m. |
| PD | Predicate disambiguation | batch_69ada4159e0481908cbbdd750f5e08c7 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:08 p.m.