Triple
T38702806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haʻikū Stairs |
E950184
|
entity |
| Predicate | causesIssue |
P195221
|
FINISHED |
| Object | trespassing problems |
—
|
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: trespassing problems | Statement: [Haʻikū Stairs, causesIssue, trespassing problems]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causesIssue Context triple: [Haʻikū Stairs, causesIssue, trespassing problems]
-
A.
raisesIssue
Indicates that one entity brings up, reports, or formally submits a concern, problem, or topic for attention to another entity or system.
-
B.
hasIssueWith
Indicates that one entity experiences a problem, conflict, or concern related to another entity.
-
C.
involvesIssue
Indicates that an action, event, or entity is related to, concerns, or includes a particular issue.
-
D.
possibleIssue
Indicates that there is a potential or suspected problem, defect, or undesired condition associated with the referenced entity or situation, though it is not yet confirmed.
-
E.
containsIssue
Indicates that one entity includes, encompasses, or has within it a particular issue, problem, or defect.
- 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_69f76f0124408190bb39c3040734846b |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fdb04ed81c8190b8feea90c1c785a6 |
completed | May 8, 2026, 9:43 a.m. |
| PD | Predicate disambiguation | batch_69fda9d6c5148190a63205b6d9b0a1b4 |
completed | May 8, 2026, 9:16 a.m. |
| PDg | Predicate description generation | batch_69fdb04d37288190969a0f39d92efb49 |
completed | May 8, 2026, 9:43 a.m. |
Created at: May 3, 2026, 4:33 p.m.