Triple
T17568969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Key-Value Observing |
E427885
|
entity |
| Predicate | commonIssue |
P13650
|
FINISHED |
| Object | crashes from dangling observers |
—
|
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: crashes from dangling observers | Statement: [Key-Value Observing, commonIssue, crashes from dangling observers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonIssue Context triple: [Key-Value Observing, commonIssue, crashes from dangling observers]
-
A.
facingIssue
chosen
Indicates that an entity is currently experiencing, encountering, or dealing with a problem, difficulty, or obstacle.
-
B.
underlyingIssue
Indicates that one situation, problem, or condition is the fundamental cause or root problem behind another.
-
C.
issues
Indicates that an entity formally produces, releases, or distributes something, such as a document, order, or resource, making it officially available.
-
D.
commonConcept
Indicates that two or more entities share the same underlying idea, notion, or conceptual meaning.
-
E.
commonLevel
Indicates that two or more entities share the same level, rank, or hierarchical position within a given system or structure.
- 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_69d889e0385081908a04b66f4dd4bd0d |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e4592f29d08190bc3de905d35af849 |
completed | April 19, 2026, 4:25 a.m. |
| PD | Predicate disambiguation | batch_69e3b4fd7d048190b54ee4c6155612a5 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:50 a.m.