Triple
T24018423
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ytterøya |
E594746
|
entity |
| Predicate | hasNoConnectionType |
P154882
|
FINISHED |
| Object | no fixed road bridge to mainland |
—
|
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: no fixed road bridge to mainland | Statement: [Ytterøya, hasNoConnectionType, no fixed road bridge to mainland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNoConnectionType Context triple: [Ytterøya, hasNoConnectionType, no fixed road bridge to mainland]
-
A.
hasModeConnection
Indicates a relationship where one entity is linked to another through a specific mode, method, or type of connection.
-
B.
hasConnection
Indicates that there exists a link, association, or relationship between two entities.
-
C.
compatibleConnection
Indicates that two entities can be connected or used together without conflict, supporting proper operation or interaction.
-
D.
hasSurfaceConnection
Indicates that two entities are directly connected or in contact at their surfaces, allowing interaction or continuity between them.
-
E.
hasAccessibleConnection
Indicates that there exists a way for one entity to reach or interact with another in a manner that meets defined accessibility requirements.
- 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_69e288be2c288190a3a46006945557f7 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d5a7b5848190849e7a0f035465b3 |
completed | April 29, 2026, 9:55 a.m. |
| PD | Predicate disambiguation | batch_69f17639d23c8190bed93434e2f9230a |
completed | April 29, 2026, 3:08 a.m. |
| PDg | Predicate description generation | batch_69f17c28b684819084eea522126463f8 |
completed | April 29, 2026, 3:34 a.m. |
Created at: April 17, 2026, 9:42 p.m.