Triple
T14284903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rainbow Bridge (approach and anchorage) |
E354143
|
entity |
| Predicate | isAccessTo |
P1017
|
FINISHED |
| Object | Rainbow Bridge main span |
—
|
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: Rainbow Bridge main span | Statement: [Rainbow Bridge (approach and anchorage), isAccessTo, Rainbow Bridge main span]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAccessTo Context triple: [Rainbow Bridge (approach and anchorage), isAccessTo, Rainbow Bridge main span]
-
A.
accessIs
Indicates that one entity has the ability, permission, or means to reach, use, or interact with another entity or resource.
-
B.
canAccedeTo
Indicates that one entity has the ability, permission, or right to gain access to or enter into another entity, resource, or state.
-
C.
hasAccessTo
chosen
Indicates that one entity is permitted to enter, use, or interact with another entity, resource, or location.
-
D.
controlsAccessTo
Indicates that one entity regulates, manages, or determines the ability of another entity to reach, use, or interact with a resource, location, or service.
-
E.
hasAccessTowards
Indicates that one entity possesses the ability, permission, or means to reach, use, or interact with another entity or resource.
- 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_69d8278d25148190abf1a8c8f5f533ad |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de697ef40c8190bea37724b28c2e99 |
completed | April 14, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69de2a88446481909cd526da97a3b70f |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:10 a.m.