Triple
T17474435
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Bross |
E425500
|
entity |
| Predicate | hasAccessIssues |
P127586
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Mount Bross, hasAccessIssues, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAccessIssues Context triple: [Mount Bross, hasAccessIssues, true]
-
A.
hasIssueWith
Indicates that one entity experiences a problem, conflict, or concern related to another entity.
-
B.
hasManagementIssue
Indicates that an entity is affected by, involved in, or characterized by a problem, deficiency, or concern related to its management or managerial practices.
-
C.
hasHumanAccess
Indicates that a human is able to access, use, or interact with the referenced entity or resource.
-
D.
hasDisabledAccess
Indicates that an entity provides facilities, features, or accommodations that make it accessible to people with disabilities.
-
E.
hasIdentityIssues
Indicates that an entity experiences confusion, uncertainty, or conflict regarding its own identity or sense of self.
- 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_69d889dbc2e88190b18ea6115e819258 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e451baa7b0819092035fec42305397 |
completed | April 19, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f341c88190adabe526d8903b05 |
completed | April 18, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69e3bbb37d148190b7f38599c06594ee |
completed | April 18, 2026, 5:13 p.m. |
Created at: April 10, 2026, 5:47 a.m.