Triple
T3236715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Einstein–Rosen bridge |
E67871
|
entity |
| Predicate | horizonStructure |
P47522
|
FINISHED |
| Object | contains event horizons |
—
|
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: contains event horizons | Statement: [Einstein–Rosen bridge, horizonStructure, contains event horizons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: horizonStructure Context triple: [Einstein–Rosen bridge, horizonStructure, contains event horizons]
-
A.
viaStructure
Indicates that one entity is connected to or accessed through a particular structural element or medium.
-
B.
segmentStructure
Indicates that one entity represents a structural or organizational subdivision (a segment) within the overall structure of another entity.
-
C.
displayStructure
Indicates that one entity presents or reveals the internal organization, layout, or arrangement of another entity.
-
D.
structureHeight
Indicates that a structure has a specific vertical measurement or height.
-
E.
rootStructure
Indicates that one entity serves as the primary or foundational structural element upon which another entity is based or organized.
- 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_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. |
| PDg | Predicate description generation | batch_69ada698eeb48190a1f5762fdd3b7b63 |
completed | March 8, 2026, 4:40 p.m. |
Created at: March 8, 2026, 3:08 p.m.